1.1 Glossary

This document uses the following terms:

activation: The process of creating a server object.

array: A Remoting Type that is an ordered collection of values. The values are identified by their position and position is determined by a set of integer indices. The number of indices required to represent the position is called the Rank of the Array. An Array is part of the Remoting Data Model and also specifies the Remoting Type of its items. For more information, [MS-NRTP] section 3.1.1.

Assignable: A reference to the ability of a Data Value to be assigned to a Remoting Type. This ability is determined by a set of rules described in the Abstract Data Model (section 3.1.1) under Data Values.

class: A Remoting Type that encapsulates a set of named values and a set of methods that operate on those values. The named values are called Members of the Class. A Class is part of the Remoting Data Model. For more information, see [MS-NRTP] section 3.1.1.

client: Synonym for client computer.

Client-Activated Object (CAO): A Marshaled Server Object (MSO) that requires an explicit activation message to create the Server Object.

data value: An instance of a Remoting Type, which can be a Class, Array, Enum, or Primitive. A Data Value is part of the Remoting Data Model. For more information, see [MS-NRTP] section 3.1.1.

Exception: A Class that indicates an error in the execution of a Remote Method. It is sent as part of the return message from a server to a client. An Exception contains a human-readable message that indicates what the error is, and can also have additional data to identify the error. An Exception is part of the Remoting Data Model. For more information, see [MS-NRTP] section 3.1.1.

lease object: A type of MSO that contains methods that control the lifetime of a server object. Although a lease object is also a server object, it does not have a lease object of its own; its lifetime is bound by the lifetime of the associated server object.

Library: Part of the Remoting Data Model. A Library is a named unit that contains a collection of Remoting Types. For more information, see Library in [MS-NRTP] section 3.1.1.

marshaled server object (MSO): A Marshaled Server Object is a Server Object that is created by a higher layer, and not in response to an incoming request. For more information on server objects, (see Server-Activated Object (SAO) for more information on the latter).. The .NET Remoting Lifetime Services Protocol [MS-NRLS] provides a mechanism for controlling the lifetimes of marshaled server objects.

member: See Class.

Null Object: Part of the Remoting Data Model. Null Object is a special value that can be used in place of an instance of a Class, Array, or String. It indicates that no instance is being specified. For more information, see [MS-NRTP] section 3.1.1.

Primitive Type: Part of the Remoting Data Model. Primitive Types are predefined Remoting Types such as Byte, Int16, Int32, Int64, and so on. For more information, see [MS-NRTP] section 3.1.1

proxy: Part of the Remoting Data Model. A Proxy forwards the invocations of Remote Methods from the client to the Server Object for execution. The Proxy contains the Request URI of the Server Object. For more information, see [MS-NRTP] section 3.1.1.

Remote Field: Part of the Remoting Data Model. A Remote Field is a remotely accessible field. For more information, see [MS-NRTP] section 3.1.1.

Remote Method: Part of the Remoting Data Model. A Remote Method is a remotely callable operation. A Remote Method can either be One-Way or Two-Way. In the case of a One-Way Method, there is no reply from the implementation. For more information, see [MS-NRTP] section 3.1.1

Remoting Type: Part of the Remoting Data Model. Class, Array, Enum, and Primitive are different kinds of Remoting Types. All Remoting Types are identified by a name that is case sensitive. For more information, see [MS-NRTP] section 3.1.1

Return Value: A Data Value that is returned as part of the results of a Remote Method invocation. For more information, see Remote Method in Abstract Data Model (section 3.1.1).

server interface: A set of method declarations that are implemented on a protocol server and are part of a FAST middleware implementation.

server object: Part of the Remoting Data Model. A server object is an instance of a Server Type. A server object is either an SAO or an MSO.

Server Object Reference: A representation of an SAO or MSO that can be passed between a client and a server. It contains sufficient information to construct a proxy to invoke Remote Methods on the SAO or MSO.

Server Object Table: A table that contains the list of available Server Objects in the server.

Server Object URI: A relative URI that identifies a Server Object in a given server. It is the path part of Request URI, excluding the leading forward slash (/).

Server Type: Part of the Remoting Data Model. A Server Type contains Remote Methods.

server-activated object (SAO): A server object that is created on demand in response to a client request. See also marshaled server object.

Singleton SAO: An SAO that is created the first time a method on its server type is called; subsequent calls to the remote methods on the server type reuse the existing SAO unless it expires. For shorter-lived SAOs, see single-call SAO.

Sponsor: An MSO that is implemented by clients to participate in the renewal process of a Server Object's lifetime.

Time-To-Live (TTL): The time duration for which a Server Object is available.

MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as defined in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.