On Nov 6, 2005, at 2:52 AM, Eric Scheid wrote:
You retrieve an entry, edit it, PUT it back, retain a copy. Later,
you edit
the entry again, and go to PUT it back... but in between those two
edits
someone else has edited the entry.
Thus, "SHOULD perform a GET on the member resource before editing"
Simply doing a GET is not a solution to the (ugly, hairy) general
problem of concurrent editing. Suppose I do a GET before I do the
PUT and someone else with a faster network gets in with their GET/PUT
in the window between them? In any case, SHOULD is inappropriate,
because it only applies in the case where you (a) are worried about
supporting concurrency and (b) don't have a more sophisticated
mechanism in place. -Tim
