[Tilesathome] Proposal: Keeping tileset as one file

[Frederik Ramm]

Hi,

> So what do you think about the proposal now, when benchmarks shows
> that keeping whole tilesets in one file is faster?

I'm not 100% convinced that the benchmarks are valid for the 
environment we're talking about; I'd have preferred someone
take the tile server code from SVN and implement stuff in 
PHP in there, but chances are the results would be similar.

I am not the one running the server but I'd say go ahead and
build it. Open questions that would still need to be addressed:

* Will tile download be done with PHP (has this been covered in
  the benchmarks - compare executing PHP code to extract data from
  a large tile with having Apache load the tile directly), or 
  will we have an Apache module for that?

* What transition strategy would we employ - surely we don't want
  to delete the current tiles, so they would either have to be 
  converted to the new format (how long would that take?), or the 
  tile download code would have to employ a "look for big tile 
  first, deliver from old data if nothing found" mechanism.

* Has the "incomplete upload" question been cleared (client uploads
  individual tiles that need to be incorporated into an existing big
  tile)? Can this be done without a significant performance penalty,
  and if not, how frequent is the situation?

Bye
Frederik

-- 
Frederik Ramm  ##  eMail frederik at remote.org  ##  N49°00'09" E008°23'33"