You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: iknopf [Submitted to the original trac issue database at 8.57pm, Sunday, 16th May 2010]
The running client analyzes the existence of "stopfile.txt" before requesting a new tileset. This works fine.
When the OSM server is too busy or down the client runs in an idle loop and checks the server for new requests every 60 seconds. Setting the stop signal ("touch stopfile.txt") during such an idle loop is ignored, and this may result in requesting a new tileset minutes after setting the stop signal.
This behavior should be changed! The client should analyze the existence of "stopfile.txt" also in an idle loop before trying to send the next request to the OSM server.
The text was updated successfully, but these errors were encountered:
Reporter: iknopf
[Submitted to the original trac issue database at 8.57pm, Sunday, 16th May 2010]
The running client analyzes the existence of "stopfile.txt" before requesting a new tileset. This works fine.
When the OSM server is too busy or down the client runs in an idle loop and checks the server for new requests every 60 seconds. Setting the stop signal ("touch stopfile.txt") during such an idle loop is ignored, and this may result in requesting a new tileset minutes after setting the stop signal.
This behavior should be changed! The client should analyze the existence of "stopfile.txt" also in an idle loop before trying to send the next request to the OSM server.
The text was updated successfully, but these errors were encountered: