Marble/TileDownload: Difference between revisions
< Marble
(New page: === 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 "...) |
No edit summary |
||
| Line 4: | Line 4: | ||
Connections to tile servers should use the "keep alive" feature. At the moment for every tile a new connection is created. | 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. | |||
Revision as of 14:18, 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.