[Tilesathome] How does a client return an unhandled request to the server?

[Sebastian Spaeth]

Norbert Wenzel wrote:
> Hi,
> 
> I was just wondering how a client returns an unhandled request to the 
> server.

http://svn.openstreetmap.org/sites/other/tilesAtHome_tahngo/requests/views.py 
in:
def feedback(...):
 > At the moment my user page[0] shows two tiles I render at the
> moment.
> 
> x,y        zoom    Priority    Last client activity   
> 2234,1420    12-17    2        3 hours, 18 minutes
> 2162,1324    12-17    1        15 minutes   

 > Both are rendered with the same client UUID (I have only one at the
 > moment). So the first question would be, does the t at h client render two
 > or more tilesets at the same time in the standard configuration? If it
 > does not, shouldn't it cancel all requests of a client (UUID) when
 > handing out a new one?

No, 1 or 2 (below) could apply

1) One was rendered but not uploaded yet to the server
2) one was rendered and uploaded but not handled yet by the server 
(upload queue)
3) it was uploaded, but the .zip was corrupt, or the server could not 
identify a valid tileset.

4) your client crashed or was stopped with ctrl-c so it couldn't hand 
back the task to the server
5a) a client bug
5b) a server bug

> So as far as I remember there is a way the client tells the server about 
> failed requests. Is that possibility not used or does my client really 
> try to render Vienna in the background?

If a client crashes and it does not return the job to the server, it is 
likely to be a client bug.


spaetz