> decision to alter the data. So the DTO must contain all data necessary > to manage concurrency, and the data-manipulation-service-call will > require certain concurrency information to be passed back to it, like > a version number for example (in the simplest of cases) or the old > field values. This will expose concurrency management to the client. > > Since I am having great trouble finding the best way to manage > concurrency issues in an efficient manner, an answer would be > extremely appreciated. Simply pointing me in the right direction would > already be of great help.
I use last modified date - when an update operation object is sent to the service to modify a domain object, it must contain the domain object's ID as well as its last modified date. This doesn't get around the issue you mention ... but it is only one extra bit of data. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
