On Mittwoch, 19. November 2008, Dirk-Lüder Kreie wrote: > it's far better to use loop mode instead of a batch mode, especially > when interacting with the tah server, for a number of reasons: > the loop mode: > a) handles uploading in the background automagically
For which I don't care if I'm running a dedicated upload_loop. > b) exits if there is a persistent fault (some external tool broken) That's why I wrote the wrapper script. The client stopped on rare cases of errors. But you are right that letting a client restart even if there are persistent errors would be a bad thing. Question is how to distinguish between rare errors and persistent errors. There are some tiles which cause errors here (the libGD error) and that's why I asked in another mail if there is a possibility to put a job back manually so that the community do not have to wait for the seven hours lasting timeout. And I didn't want to let this rare cases stop the loop. > c) better handles client-server interaction. > d) offers a chance to do auto-tuning of the maxComplexity stuff. > > basically it handles everything better where the knowledge of previous > client behaviour is needed to decide how to proceed. ...where... Regards Andre
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
