|
Hi, Slide transactions are based on JTA (which stand for java transaction api). Each slide store is an XAResource. When you do a begin/commit/rollback (in the NamespaceToken) Slide transmit to JTA, and JTA call slide 's store back. I think it use one-phase commit (but not sure). You can add (enlist) any other XAResource instance to the transaction and then the methods commit/rollback will be called. I hope this will help you a little. Guillaume Bailleul wrote: Hi all, I'm looking for documentation on how work transactions in slide.I'm trying to make a working failover system on something like this: a slide server stores files on nfs partitions. If the slide server breaks, a second server do the job. I'm looking how to make it possible, what to do with started transactions, how to come back to the primary machine. To do this, I need to understand how transactions works internally with slide. So if you have some documentation, or some time ... Thanks for your help, Best Regards Guillaume --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Honoré David N. Projet DISSCO (http://www.meteo.be/DISSCO/) email: [EMAIL PROTECTED] tel: 02 37 30 530 |
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
