On Tue, Oct 14, 2008 at 11:11:26AM -0400, Matthias Julius wrote: > spaetz <[EMAIL PROTECTED]> writes: > > > 1) The server sends the request priority to clients now. The idea was > > that the client can then decide whether to fetch from the live API > > (interactive PRIO 1 requests) or from one of the read-only mirrors > > (changed tiles requests and bulk requests). > > Is this actually necessary? If the mirrors are only a few minutes > behind the main API the tah server could just make sure every request > has sat at least for 5 min in the queue before handing it out.
I leave that decision to client developers. You have the info, now use it or ignore it :-). But keep in mind the main purpose of [EMAIL PROTECTED] (in my opinion) is to "provide visual feedback of edits as quickly as possible". I do expect to be able to edit some area, upload the changes, press "r" for render and have the result shown in 2 minutes (in a non-dense area). Keeping requests purposefully in the queue is nothing that the server will ever attempt to do. I would therefore opt for a possbility of immediate and live API rendering. Most requests are either auto-requests or bulk requests that are old enough to safely use the mirrors. > It will eventually be in the meta data (needs to be implemented) but > the server can also have it POST variables. And it will also be in > the file name because that's what the files happen to be stored under. See separate mail. This is basically implemented server side, bar the problem of empty tilesets. spaetz _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
