Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This protocol extends the server and client roles defined in the .NET Remoting Protocol [MS-NRTP] by defining Remoting Interfaces to be implemented by each role. For each Remoting Interface, the client side is simply a pass-through. That is, no additional timers or other state information are required on the client side. Calls made by the higher-layer protocol or application are passed directly to the transport, and the results returned by the transport are passed directly back to the higher-layer protocol or application.
This protocol extends the server role defined in the .NET Remoting Protocol Server Details ([MS-NRTP] section 3.2) in the following ways:
The server implementation MUST register a Server-Activated Object (SAO) that implements the IActivator (section 3.1) interface. The Server Object URI of the SAO MUST be "RemoteActivationService.rem".
Each Server Object that participates in the lifetime management MUST implement MarshalByRefObject (section 3.2).
Each Server Object that defines one or more Remote Fields MUST implement Object (section 3.5).
The ILease Abstract Data Model (section 3.3.1) extends the .NET Remoting Protocol Server Abstract Data Model ([MS-NRTP]section 3.2.1) in the following ways:
Associates a Lease Object with each Server Object in the Server Object Table.
Updates the TTL of the Lease Object on each invocation of an application-defined Remote Method.
This protocol extends the client role defined in [MS-NRTP]section 3.3 in the following way:
The client MAY implement the ISponsor (section 3.4) interface to participate in the lifetime management of the Server Object.<8> By implementing the ISponsor interface, the client is also acting in the server role defined in [MS-NRTP]section3.2.