In RAP scenario, the etag field is mentioned in the Behavior Definition. Building OData Services : Concurrency handling using ETag with Entity Hash.Building OData Services : Concurrency handling using ETag with time-stamp field.They way this works is similar to service built using SEGW and below posts cover those scenarios. UPDATE operation checks whether the etag matches, if the etag does not match it means that the entity is changed already by someone else and the UPDATE operation is rejected. The etag field usually contains a timestamp, a hash value, or any other versioning that precisely identifies the version of the data set. Optimistic Concurrency Control– assumes that the likelihood of a concurrent write is rare and so allows the operation to continue and only check at the final moment while updating the data Optimistic Concurrency Control.Pessimistic Concurrency Control (Locking)– assume that concurrent writes will occur and hence protects it by aggressively locking out resources.If simultaneous update requests are received, the service should allow only one update at a time and reject other updatesĬoncurrency needs to be managed as we need to prevent concurrent and interfering database access of different users and ensures that data can only be changed if data consistency is assured.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |