Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

reconsider connection timeout / retry cycle in applet #382

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment
Closed

reconsider connection timeout / retry cycle in applet #382

openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment
Assignees
@openstreetmap-trac
Labels
Component: applet Priority: minor Resolution: wontfix Type: enhancement

Comments

@openstreetmap-trac
Copy link

Reporter: writetodan[at]yahoo.com
[Submitted to the original trac issue database at 8.47pm, Monday, 26th February 2007]

currently the failure of (e.g.) a node-creation call to the server due to socket timeout, and subsequent retry/retries can cause multiple identical API calls to succeed - in this case leading to multiple overlapping nodes.

perhaps creation calls to the api deemed failed other than by server response code should only be retried after GET of relevant bbox to ascertain whether such a primitive was indeed created.

a ticket has also been logged against API.
@openstreetmap-trac openstreetmap-trac self-assigned this Jul 23, 2021
@openstreetmap-trac
Copy link
Author

Author: osm[at]bcowan.fastmail.co.uk
[Added to the original trac issue at 6.40pm, Sunday, 25th November 2007]

Applet is gone.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@openstreetmap-trac openstreetmap-trac

Labels
Component: applet Priority: minor Resolution: wontfix Type: enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@openstreetmap-trac