[Tilesathome] Tileset as one file v2

[spaetz]

On Wed, Oct 08, 2008 at 08:57:55AM -0400, Matthias Julius wrote:
> > * ''userid'' is set twice, once in the beginning of the file and once
> > as "metadata" in the end. Do we really need to set it twice? I'd
> > rather not.
> 
> Techically, the userid doesn't need to be in the header.  That's why
> it is in the meta data section.  I left it in the header for
> compatibility reasons.  This way v2 is a pure extension of v1 and v1
> is a special case of the v2 format (except that v1 has no meta data).

The userid is a bit special, in that it is the only value that can't (and shouldn't) be set by the client as it only applies within the context of a single server installation. So treating it a bit separately is ok IMHO.

Now, it still requires the server to both modify at the beginning and the end of the file in v2. Ideally, the server could leave the metadata section alone and have just the user filled in data tere.

> > - we have the base zoom level at the end and the number of zoom levels
> > and the first zoom level in the beginning of the file. Is this
> > inconsistency needed? Why not put the base zoom level in the last byte


> Maybe the pain killers have thrown you off here, too. ;-)

Yes, they have, I was assuming the "size" variable is the base-z. My bad. 

> mtime might get lost when copying a file across different systems or
> media like HTTP.  I think it is better if all relevant information is
> contained in the file.  This is worth the 25 bytes it will take, IMHO.

(You mean the 183 MB per layer :-) (if all 16m tileset files were stored)

> The beginning of the meta data section states that it consists of
> lines of plain text.  I think this excludes a binary representation of
> the data.  Do I need to clarify this a bit more?

Yes, as e.g. I didn't know which format to expect.

> See above.  Everything is stored in plain text strings.

mmh, bloaty :-). ok 

> I didn't even know the server is maintaining an internal layer
> number.  And the client certainly won't know what it is.  So I meant
> the layer name.
 

> I won't do anything major to the client besides a bit tidying up and
> updating comments until the current _unstable has been migrated to
> stable.  After that I will start working on the client side changes
> necessary for uploading tileset files.

Can you tell me how I can use a current client for testing to see if uploading tileset files work? Is there a config option or a magc switch? Would be great to be able to test this with a live client.

spaetz