Is concurrency and idempotency mutually exclusive for a REST web service or can it be done so a service can be both concurrent and idempotent? Using a optimistic lock methodology like using Version property seem to be preventing a method to be idempotent if I'm not mistaken?For example, let's say you have User A wanting to update Person.NameCurrent Person.Version = 1User A sets Person.Name = Name XPerson.Version = 2Now the Person.Version = 2User A send same request, with Person.Version = 2 value. It fails because you expect the Person.Version value 3.
Idempotency and concurrency in a REST web service
design;rest;web services