 |
 |
 |
 |
|
 |
|
 |
|
 |
|
 |
|
|
|
|
|
|
|
|
|
|
|
|
Brian E Carpenter wrote:
As far as I can tell, the proposal places the burden for ensuringatomicity entirely on the server. However, PATCH is explicitly not idempotent. If a client issues a PATCH, and the server executes the PATCH,but the client then fails to receive an indication of success due to an extraneous network glitch (and TCP reset?), then what prevents the client issuing the same PATCH again? In other words, absent a two-phase commit, there appears to be no transactional integrity.
How is this different from PUT or POST? If you need repeatability of the request, just make the request conditional using "if-match"...
BR, Julian
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.