[Tilesathome] Proposal: Keeping tileset as one file

[Dirk-Lüder Kreie]

spaetz schrieb:
> On Thu, Jun 26, 2008 at 10:37:41AM +0200, Frederik Ramm wrote:
> 
>> If client A uploads a tar with tiles 1, 2, 3, and later B uploads a tar 
>> with tiles 10, 11, 3, then you have two choices:
> 
> It seems a reasonable policy change to require the uploading of complete tilesets. The bottleneck is always going to be the server, so why not push as much work to the clients as possible and make it as easier for the server.

There are some problems with tilesets that even now are too big for the 
current maximum upload size (but can be adapted in php.conf)
Secondly the clients have a renderFullTileset option already which can 
be set quite easily via svn.

> If we mandate the uploading of full tilesets as tar files and it get's as easy for the server to process that as to move it to the appropriate location, then I'm all for it. I'm just not going to code it.

Same here. So apart from the coding of the serverside stuff we "just" 
need to adapt the php.conf (or whatever then handles the uploading 
itself) to allow for larger POST and upload files (I think there were 2 
config options that had to be modified)
and the clientside config option for maximum upload size (zipHardLimit IIRC)

> Marking blank tiles could still be done by passing the appropriate blankness info through a special HTTP call.

however we will have all that info inside our "full Tileset" uploads.

we might want to run a simplifier for ocean-tiles from time to time.

or we need to calculate the overhead of storing the entire sea via such 
files...

-- 

Dirk-Lüder "Deelkar" Kreie
Bremen - 53.0952°N 8.8652°E

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstreetmap.org/pipermail/tilesathome/attachments/20080630/6ada62f4/attachment.pgp>