| Platform SDK: Transaction Server |
[This product will work only on Windows NT 4.0 versions and earlier. For Windows 2000 and later, see COM+ (Component Services).]
The following table contrasts MTS components with base client applications.
| MTS components | Base clients |
|---|---|
| MTS components are contained in COM dynamic-link libraries (DLLs); MTS loads DLLs into processes on demand. | Base clients can be written as executable files (.exe) or dynamic-link libraries (.dll); MTS is not involved in their initiation or loading. |
| MTS manages server processes that host MTS components. | MTS does not manage base client processes. |
| MTS creates and manages the threads used by components. | MTS does not create or manage the threads used by base client applications. |
| Every MTS object has an associated context object. MTS automatically creates, manages, and releases context objects. | Base clients do not have implicit context objects. They can use transaction context objects, but they must explicitly create, manage, and release them. |
| MTS objects can use resource dispensers. Resource dispensers have access to the context object, allowing acquired resources to be automatically associated with the context. | Base clients cannot use resource dispensers. |