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?
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.
Just idle thoughts on a quiet Friday afternoon.
As an aside, I thought there may have been some sort of stripe rendering issue
in the Manchester area as a lot of roads seemed to end at the same north-south
line, although more major ones went through the right hand edge of the tile
which confused me. When I switched to edit mode in Potlatch the reason became
clear - it was where the Yahoo imagery ended, and people have been busy adding
highway=roads ready for this weekend's mapping party there.
Ed
_______________________________________________
Tilesathome mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/tilesathome
