Marble/TileDownload: Difference between revisions
< Marble
No edit summary |
No edit summary |
||
Line 8: | Line 8: | ||
Separation between http download and tile providing since http download is needed for wikipedia (and perhaps other stuff) integration also. | Separation between http download and tile providing since http download is needed for wikipedia (and perhaps other stuff) integration also. | ||
=== Design proposal === | |||
to be done |
Revision as of 14:50, 18 March 2009
Design considerations
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.
Design proposal
to be done