The state information can be kept in:
-
Client Side: Client application can keep the state of an object while making object in server stateless. This approach works fine if the object has a small state information so that it does not introduce extra overhead for transferring this information to the server object for each function call. But, it is unreasonable if the state information requires a large amount of data.
-
Database State Storage: Object can store its state into a database through ODBC API or OLE DB interface. This approach is best suited if the object stores its durable state instead of every temporary state since it will create another bottleneck on the database.
-
Shared Property Manager: The Shared Property Manager is defined by MTS as a resource for storing and sharing state among multiple objects in the server process.
|
