The way that MTS handles transactions and resources certainly has implications
for the client. On the whole, the syntax for coding a client does not change.
It is extremely important, however, for a client developer to know the inner workings
of the MTS object it is calling.
The client developer needs to be aware of exactly which methods will call SetComplete
or SetAbort. Because it is possible that an MTS object was designed to be stateless,
the unaware developer could be in for a big surprise when properties lose their
values or when methods fail because they depend on some internal variable whose
contents have been erased.