-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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.
| 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.
- --
Dirk-Lüder "Deelkar" Kreie
Bremen - 53.0952°N 8.8652°E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJAhlaFUbODdpRVDwRAjqWAJ9YIo7/IyCh64RfbYgF4x70mHdU0gCgjYwC
96Reea11HiSrg6zIOm9mJ8s=
=BP4c
-----END PGP SIGNATURE-----
_______________________________________________
Tilesathome mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/tilesathome
