[Tilesathome] Some questions on client behaviour

[Sebastian Spaeth]

Matthias Julius wrote:
>> 1.) Why is the client sleeping for 60 seconds when rendering is finished and 
>> the client is not in loop mode?
>>
>> 2.) Why is the client sleeping for 60 seconds before getting a new job when 
>> the server upload queue is too full? Isn't sleeping before uploading the 
>> rendered tiles enough?

I thought we'd get rid of the upload queue check as the server will only
hand out new jobs if the server queue is not too busy. IMO it can go
away completely.

>> 3.) Why is the client getting a new job after case 3.) even if there is a 
>> stopfile?
To understand recursion you have to understand recursion? :-) I guess
you mean case 2) ?

>> 4.) Why do I have to start a separate upload process after rendering when the 
>> client is not in loop mode?
>>
>> Suggestion to 1.) Implementation of a "batch mode" where this sleep is 
>> skipped. This would help me a bit, since I wrote a small bash script which is 
>> checking a central stopfile so that I only have to set the stopfile once for 
>> all clients. (You can find the script at the end of this mail.) 

Your proposals seem mostly to aim at making non-loop mode better suited
for looping, when the real bug seems to be that loop mode doesn't  honor
stop files?

>> Suggestion to 4.) Implementation of a new option to do rending and uploading 
>> in one step. Normally I would have expected that this is the default but 
>> changing the behavior now could probably cause problems with some other 
>> control scripts.

This is what happens in loop mode, which you might want to use :-)

Other than that, yep there are probably more inconsistencies and
unneccessary things like the one you mentioned in the client code.

spaetz