| 1 |
MTS supports an just-in-time activation by late object creation and early object deactivation.
|
| 2 |
MTS tries to utilize the resources of server so that servers can be more scalable than it would be.
|
| 3 |
The real activation of an object is delayed until client invokes the first function call on the interface.
|
| 4 |
The deactivation of an object does not wait until the reference counts drops to zero, MTS can deallocate the object while some client still has the valid reference to this object. In a case a client wants to use the same interface again then MTS recreates the copy of the object and client never knows which object is in use.
|
