Redundant Informix databases and Tuxedo/T

Hello! Yesterday I received a message from the Informix mailing list about the possibility of writing an application that could use redundant Informix databases. The posting was made by Dan Hepner, but perhaps others can give me some insight too. Dan writes: >> It should be possible "any time now" to write an application >> which can use redundant Informix databases, >> and using the Tuxedo/T TP Monitor, effect an atomic commit >> across both, with the application being responsible to react >> to failures of the redundant system. The most reasonable >> first target for discussion of availability would seem to be >> your hardware vendor, or Informix. My questions and comments: (1) What is the "Tuxedo/T TP Monitor" and how would it (a "monitor") be used with respect to redundant database transaction processing? (2) Since Informix will only allow an application to access ONE database at a time, it seems that the application needs to keep track of the 'before' and 'after' states of the records being modified to be able to perform a 'rollback'. (3) This sounds somewhat like implementing a "two-phase commit" IN THE APPLICATION as opposed to within the database engine. (4) Does anyone know of Informix even PLANNING this type of functionality in the near future? (5) Which Informix Database product is this a reference to? Standard Engine? On-Line? I am truly interested in any/all responses because we have a need for this type of functionality in our product. If there's a reasonable solution, I'd like to pursue it. Thanks in advance for any help. Joseph P. Tokarski email: tokarski@nms.gdc.portal.com Senior Software Engineer phone: (203) 758-1811 ext. 7067 General DataComm, Inc.