3.5.4 Message Processing Events and Sequencing Rules
This DCOM interface inherits the IUnknown interface. Method opnum field values start with 3; opnum values 0 through 2 represent the IUnknown_QueryInterface, IUnknown_AddRef, and IUnknown_Release methods, respectively, as specified in [MS-DCOM].
Methods with opnum field values 3 through 33 are defined in section 3.1.4, and those with field values 34 through 39 are defined in section 3.3.4.
The IMSAdminBase3W RPC interface extends the IMSAdminBase2W interface by providing a method to return the nodes of children from a specified metabase path. The IMSAdminBase3W protocol does not maintain client state information; the protocol is stateless.
A RPC sequence is a client/server session that includes a security context phase and requests to call remote procedures. For a connection-oriented RPC, the session also includes a binding phase. The RPC client supplies the necessary security information, and for connection-oriented RPCs it also supplies binding information, such as interface name and server endpoint. The sequence of subsequent RPC calls in the session is implementation-specific.
Methods in RPC Opnum Order
|
Method |
Description |
|---|---|
|
Returns all child nodes of a specified path from a supplied metadata handle. Opnum: 40 |
When a remote call is made, the UUID and version number of the interface are specified in the abstract_syntax and abstract_syntax_vers fields of the incoming RPC_BIND packet, as specified in [MS-RPCE].