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: Richard [Submitted to the original trac issue database at 2.52am, Sunday, 15th June 2008]
When the server is being slow (or one's connection is crap), it's quite common that a way is written, but that the response doesn't get back to Potlatch.
Perhaps (either by a prompt, or automatically) Potlatch could send a query like: "tell me what nodes exist with this co-ordinate, and that co-ordinate, and the other... and what way connects them". That way it could find whether the way really has been written.
The other way of doing it would be to have some form of id for each upload, and to be able to query whether it's written or not. Would need some server-side storage though. (Perhaps as a user pref!)
The text was updated successfully, but these errors were encountered:
Reporter: Richard
[Submitted to the original trac issue database at 2.52am, Sunday, 15th June 2008]
When the server is being slow (or one's connection is crap), it's quite common that a way is written, but that the response doesn't get back to Potlatch.
Perhaps (either by a prompt, or automatically) Potlatch could send a query like: "tell me what nodes exist with this co-ordinate, and that co-ordinate, and the other... and what way connects them". That way it could find whether the way really has been written.
The other way of doing it would be to have some form of id for each upload, and to be able to query whether it's written or not. Would need some server-side storage though. (Perhaps as a user pref!)
The text was updated successfully, but these errors were encountered: