TRANSACTION BEGIN PUT file1 (still not visible from outsite tx) PUT file2 (still not visible from outsite tx) TRANSACTION COMMIT
After that file1, file2 are correctly committed and globally visible...
and
TRANSACTION BEGIN PUT file1 (still not visible from outsite tx) PUT file2 (still not visible from outsite tx) TRANSACTION ROLLBACK
After that file1, file2 are correctly rolled back...
This is just a proof of concept and the biggest part of the work is still to be done, but I am in good faith, it will be manageable with moderate changes to the Slide core.
I will be off on holiday for the next two weeks, but will continue work on this topic after my return.
Oliver
Oliver Zeigermann wrote:
Folks!
Daniel and I are currently evaluating if there is a simple and straight forward way to add external transaction management to Slide. Opposed to activity, workspace, etc. concepts this is for short term transactions like the ones you might know from relational database systems. The goal of this approach is to finally have a connector from application servers to an external Slide server or more generally have transactional support from clients of any kind (the J2EE server would be the client using the JCA).
Daniel has already checked in code for a new transaction method. This code is to be considered experimental, but does not break anything.
I will keep you up to date with the progress we make.
Cheers,
Oliver
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
