[Tilesathome] Request Priorities now sent to the client

[Matthias Julius]

spaetz <osm at sspaeth.de> 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.

> 3) I have started work to deal with uploaded tileset files directly on
> upload, which would eliminate the extra upload processor and the
> upload queue. Not functional yet. Matthias, should the server deduce
> the x and y values from the tilesetfile metadata, or will these values
> be delivered as HTTP POST vars?

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.

Belt and suspenders, I guess.

Matthias