Marble/TileDownload: Difference between revisions

Revision as of 14:31, 18 March 2009

Downloading of tiles should be in separate threads so that each connection to a tile server has its own thread.

Connections to tile servers should use the "keep alive" feature. At the moment for every tile a new connection is created.

Perhaps create an (abstract) interface / abstract class TileProvider? Not sure, if there is an use case.

Separation between http download and tile providing since http download is needed for wikipedia (and perhaps other stuff) integration also.

Revision as of 14:18, 18 March 2009 (view source) Tampakrap (talk \| contribs) No edit summary ← Older edit		Revision as of 14:31, 18 March 2009 (view source) Tampakrap (talk \| contribs) No edit summary Newer edit →
Line 6:		Line 6:

	Perhaps create an (abstract) interface / abstract class TileProvider? Not sure, if there is an use case.		Perhaps create an (abstract) interface / abstract class TileProvider? Not sure, if there is an use case.

			Separation between http download and tile providing since http download is needed for wikipedia (and perhaps other stuff) integration also.