Dirk-Lüder Kreie <[EMAIL PROTECTED]> writes:
> Ed Loach schrieb:
> | Could the stopfile.txt existence be checked more often, and the
> current request get put back if it is encountered? I'm only thinking
> about it as the amount of time I'm waiting for it to timeout on the
> downloads before it then decides there is nothing to compress and
> finally find the stopfile seems to be fairly long. Having had a quick
> look it could be done in some places by raising a non-fatal TilesetError
> in an appropriate way - something like:
> |
> | if (-e "stopfile.txt")
> | {
> | throw TilesetError "Stopfile.txt found", "Stopfile";
> | }
> |
> | but perhaps as a CheckForStopfile method so it can be called from
> various different points?
>
> What you want is a breakfile, not a stopfile.
Or Ctrl-C. (Does that work on Windows?)
I have on my TODO list to make the client catch this and return the
job to the server.
>
> | Alternatively, or perhaps additionally, if a client could tell there
> was an incomplete request on startup perhaps it could either try putting
> it back or resuming/restarting, perhaps based on the age of the request?
> I'm not sure there is any easy way to tell that information at present
> though. I'm thinking about after power cuts or other unscheduled
> interruptions.
>
> It would need to check for currentness, and in case of power failures,
> interity, otherwise that would not match with our goal to supply the
> freshest map possible.
The client could save the timestamp when it got the job and just redo
it from the beginning including OSM data download if it got the job
less than maybe 5 hours ago. To let the client continue where it was
interrupted would not be that trivial.
But, I don't think this is worth the trouble. Currently if a client
doesn't return the results of a job someone else will get it. Someone
could analyze the server log and get the turnaround times for all
requests. Then we could set the request timeout to the time in which
99% of jobs were returned or so.
Matthias
_______________________________________________
Tilesathome mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/tilesathome
