3.2.5.2.5 INtmsSession1 Interface
This interface is used to open and close sessions. Establishing a session is a prerequisite to using the other functions of the RSM Remote Protocol.
The INtmsSession1 interface is implemented by servers to support session management. The UUID for this interface is "8DA03F40-3419-11D1-8FB1-00A024CB6019". The version for this interface is "1.0".
INtmsSession1 inherits the IUnknown interface ([MS-DCOM] section 3.1.1.5.8). Opnums 0, 1, and 2 are IUnknown::QueryInterface, IUnknown::AddRef, and IUnknown::Release.
Methods in RPC Opnum Order
|
Method |
Description |
|---|---|
|
Sets up a session with the server, with strings encoded using Unicode. Opnum: 3 |
|
|
Sets up a session with the server, with strings encoded using ASCII. Opnum: 4 |
|
|
Closes a session. Opnum: 5 |
|
|
Submits an operator request, with strings encoded using Unicode. Opnum: 6 |
|
|
Submits an operator request, with strings encoded using ASCII. Opnum: 7 |
|
|
Waits for an operator request. Opnum: 8 |
|
|
Cancels an operator request. Opnum: 9 |
|
|
Completes an operator request. Opnum: 10 |
|
|
Imports the state of the server at the next server restart. Opnum: 11 |
|
|
Exports the state of the server. Opnum: 12 |
|
|
Opnum13NotUsedOnWire |
Reserved for local use. Opnum: 13 |
|
Registers a client to receive change notifications for a type of object. Opnum: 14 |
|
|
Unregisters a client from receiving change notifications for a type of object. Opnum: 15 |
|
|
Sends a notification to all registered sinks. Opnum: 16 |
In the preceding table, the phrase "Reserved for local use" means that the client MUST NOT send the opnum, and the server behavior is undefined<75> because it does not affect interoperability.
All methods MUST NOT throw exceptions.