create-node timeouts and retries can create multiple identical nodes #381
Comments
|
Author: tom[at]compton.nu The basic problem is that the client times out and gives up, but the server waits a bit longer and does get around to handling the pending request. Not sure there is much we can do about this. |
|
Author: karl.guggisberg[at]guggis.ch See Clients could add a unique request ID to every request (i.e. a GUID?), server makes sure that every request is processed at most once. Additional requests with the same request ID would be ignored by the server. A warning could be replied to the client for duplicated requests. |
|
Author: iandees Cleaning old tickets. |
Reporter: writetodan[at]yahoo.com
[Submitted to the original trac issue database at 12.12am, Thursday, 22nd February 2007]
it appears as if when a node-creation call to the API times out and is aborted (e.g. through exceeding socket.timeout setting in HttpClient in applet's Adapter), one or automatic more retries to the API can result in multiple identical nodes being created.
unsure if/what should be done on API-side. (ticket also created against applet)
The text was updated successfully, but these errors were encountered: