Antuane,
Is this not the normal way of using optimistic concurrency, all the time you
are building an update set and goes on as long as it is right?
Then at the end it can happen that a user has build a complete update set,
and than just a second before that another user has made a change, which
destroys the correctness of the updateset.
Than that should not update however report to the user that it is not be
done.
There can be investigated what gives the error (what is changed in the
meantime) and create a new updateset while the right things are in it
already or let the user do it all over again with the new information (what
is of course the most simple).
Just my thought, when I understand your question well.
Cor
"Antuane" <An*****@testing.com.net>
..
any one have any idea how transactions could be enabled in webservices.
i.e., suppose i've got 2 methods - one to add a contact, & the other to
set
some miscellaneous details for the contact, in a webservice.
Now the client uses the above two methods & if the client is happy with
the
return values of the above two methdos, ONLY then are the changes made on
the server to be commited. (there'd be three other methods,
begin-transaction, end-transaction & commit-transcation.
Any idea or concepts on achieving this.
(just as we have transcations with an SQL server, i'd like for the client
to
have transcations on his/her end with the webserver).
