DSA, multiple updates and concurrency

Topics: CAB & Smart Client Software Factory
Aug 21, 2007 at 1:52 PM
Hi.

Our smart client application uses some Disconnected Service Agents to communicate with our server-application (wcf).
To handle concurrency issues, we use a datetime field, which is being updated only by the server (never by the client).

How does a DSA behave, when updateing the same record multiple times when offline?

As far as I know, each request gets its own unique id. When the connection is reestablished, the first request gets dispatched and will succeed. The server changes the datetime field (concurrency). The second request will fail, for at the moment it was being generated, the concurrency datetime field had a different value. Is this correct?

Is there a way to avoid this scenario? Can one replace requests for the same data automatically?

I hope I was able to describe our problem well enough - and sorry for my bad english.

Thanks a lot for your help in advance.