On Tue, Oct 14, 2008 at 09:35:08PM +0200, Florian Lohoff wrote:

> I'd let clients upload to a temporary area and check for an empty
> tileset before moving. I guess later in the game we'd need a tileset
> file validator to make shure clients did not mess up pngs, pointers etc
> by accident or intentionally.

We don't do any of that right now and if possible I would like to avoid having 
the server to do quality checks on each upload. The whole idea behind uploading 
tileset files is to make the server do less work and remove a potential central 
bottleneck, not having it do more work than it does now.

Also, I would like to keep the server as dumb as possible with regard to the 
underlying files. If I start doing quality checks, people will want it to check 
whether colors are ok and their skiing lifts have rendered properly (SCNR). 
These tests should probably be done, but they should be done on the client side 
in a distributed manner.

We currently stall out at something around 3k/requests (ie 9k uploads/h). In 
order to increase that limit, we need to make that faster.

_______________________________________________
Tilesathome mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/tilesathome

Reply via email to