Transaction service for ICE
We are looking into ICE as a replacement to our CORBA infrastructure, however, there is one thing that we need more than probably any other service that - and that's the transaction service. Is there any efforts being made to develop a transaction service for ICE yet? I would like to know this very much. Thank you.
Martin
Martin
0
Comments
May be the "persistance service" with Freeze is a good feature to simulate or support a transaction service ?
Sorry if this sounds kind of redundant or obvious, but just wanted to hear your opinion. I am impressed with the clarity of thought that went into ICE, and after reading a Usenet diatribe on this issue (which I accidentaly found out when I was looking for some CORBA info
The opengroup defined the XA specification which provides a standard API to a database which can be used to implement distributed transactions. XA itself is independant (in theory) of the underlying database, and independent of any distributed messaging technology (such as OMG CORBA and the OTS).
It is typically used by a TP vendor to tie the TP processing to the underlying database -- that is TP uses XA to control the transactions (start, end, commit, abort, etc). So, therefore, XA would not be implemented 'on top' of Ice, but rather the other way around.
Regards, Matthew