There is no predetermination regarding which application components are to participate in a transaction. TIP transaction trees can therefore be built-up involving many arbitrary TIP URL aware applications, using many different communications mechanisms, and many different transaction managers. As new communications protocols are developed, these can be used together with TIP to provide transactional versions of such protocols. The need for development and implementation of a new transaction protocol for every new communications scheme is obviated. Because of its simplicity and utility, it is expected that TIP will be widely implemented.
TIP therefore offers a practical solution for very heterogeneous transactional interoperability.
Reference Model Version 2 . Evans, K., J. Klein, and J. Lyon. Transaction Internet Protocol Requirements and Supplemental Information . IETF RFC 2372. Transaction Internet Protocol Version 3.0 .