1.1 Glossary
This document uses the following terms:
AppDomain: An isolated environment where .NET applications execute. AppDomains provide isolation, unloading, and security boundaries for executing .NET managed code. For more information see [MSDN-AppDomain].
argument: A named Data Value that is passed as part of a Remote Method invocation or returned as part of the results of a Remote Method invocation. For more information about Remote Method invocation, see [MS-NRTP] section 3.1.1.
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.
authentication: The ability of one entity to determine the identity of another entity.
base64 encoding: A binary-to-text encoding scheme whereby an arbitrary sequence of bytes is converted to a sequence of printable ASCII characters, as described in [RFC4648].
binary format identifier: A string that is contained in the message frame. The binary format identifier identifies the serialization format of the message content as specified in [MS-NRBF]. Its value is 'application/octet-stream'.
Call Context: A mechanism to pass data that is not part of the method Arguments between client and server. It is a collection of name-value pairs that is carried with the execution of a Remote Method. This collection is sent along with other method Arguments from client to server, and is transmitted back, along with the Return Values and output Arguments, from the server to the client. For more information, see [MS-NRTP] section 1.3.
certificate: A certificate is a collection of attributes and extensions that can be stored persistently. The set of attributes in a certificate can vary depending on the intended usage of the certificate. A certificate securely binds a public key to the entity that holds the corresponding private key. A certificate is commonly used for authentication and secure exchange of information on open networks, such as the Internet, extranets, and intranets. Certificates are digitally signed by the issuing certification authority (CA) and can be issued for a user, a computer, or a service. The most widely accepted format for certificates is defined by the ITU-T X.509 version 3 international standards. For more information about attributes and extensions, see [RFC3280] and [X509] sections 7 and 8.
channel: An entry point through which a server gets connection requests from a client. A Channel contains information about the chosen transport (for example, TCP) and supports one or more formats (for example, binary or SOAP). A server can host one or more Channels. For more information, see [MS-NRTP] section 3.2.3.
channel URI: A part of a Request-URI message. It contains the URI scheme, host name, and optionally a port number for a channel, as described in [RFC3986].
chunked encoding: A transport-specific encoding of message content that breaks the content up into a series of octet segments. This allows dynamically produced content to be transferred, along with the information necessary for the recipient to verify that it has received the full message. For more information on HTTP chunking, see HTTP Transport (section 2.1.2). For more information on TCP chunking, see TCP Transport (section 2.1.1).
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.
credential: Previously established, authentication data that is used by a security principal to establish its own identity. When used in reference to the Netlogon Protocol, it is the data that is stored in the NETLOGON_CREDENTIAL structure.
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.
delegate: A user or resource that has permissions to act on behalf of another user or resource.
digest: The fixed-length output string from a one-way hash function that takes a variable-length input string and is probabilistically unique for every different input string. Also, a cryptographic checksum of a data (octet) stream.
Digest Access Authentication: A mechanism built on top of HTTP that allows a client program to provide credentials without having to send a user name and password in plaintext when making a request. For more information, see [RFC2617].
Enum: A Primitive type whose members are constrained to a set of values. The Primitive type is considered to be an underlying Remoting Type of the Enum. Each value has a name associated with it. An Enum is part of the Remoting Data Model, and an abbreviation for "enumeration." For more information, see [MS-NRTP] section 3.1.1.
Envoy Sink Information: A Data Value associated with a Server Object or Server Type. When a Server Object reference to an associated Server Object or Server Type is transmitted to a client, the Envoy Sink Information is sent as well. The Envoy Sink Information contents are undefined, and can be used by application authors to send arbitrary data. For more information, see the example in Protocol Overview (section 1.3).
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.
Generic Argument: A formal argument used in a Generic Type or a Generic Remote Method to represent a parameterized Remoting Type. Generic Arguments can be referenced in the Class or the method as opaque Remoting Types. They are replaced by the actual types when the Class or the method is used. For more information, see Generic Type and Methods in [ECMA-335].
Generic Remote Method: A Remote Method that is parameterized by one or more Remoting Types. The method caller has to provide the actual Remoting Types (in addition to the Input Arguments). For more information, see [MS-NRTP] section 3.1.1.
Generic Type: A Class, Server Type, or Server Interface that is parameterized by one or more Remoting Types. A Generic Type contains GenericArguments as a placeholder for the parameterized Remoting Types. A Generic Type cannot have any instances. For more information, see Generic Types and Methods in [ECMA-335].
Hypertext Transfer Protocol (HTTP): An application-level protocol for distributed, collaborative, hypermedia information systems (text, graphic images, sound, video, and other multimedia files) on the World Wide Web.
Input Argument: A named Data Value that is passed as part of a Remote Method invocation from the client to the server. For more information, see Remote Method in the Abstract Data Model (section 3.1.1).
Instantiated Generic Type: A Remoting Type that is the result of replacing the Generic Arguments of a Generic Type with the actual Remoting Types. An Instantiated Generic Class can have instances. For more information, see Generic Types and Methods in [ECMA-335].
IPv4 address in string format: A string representation of an IPv4 address in dotted-decimal notation, as described in [RFC1123] section 2.1.
IPv6 address in string format: A string representation of an IPv6 address, as described in [RFC4291] section 2.2.
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.
local name: A string value that, together with an XML namespace, identifies XML element and attribute names. For more information, see [XMLNS-2ED].
logical call ID: An optional string value that identifies the logical thread of execution. This value is passed as part of the Call Context and can be used in implementation-specific local threading models on the server.
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.
message content: The serialized body of a message.
message frame: A transport-specific structure for adding headers to a message. When using HTTP, message frames are represented as HTTP headers. For more information, see HTTP Transport (section 2.1.2). When using TCP, message frames are represented as defined in Message Frame Structure (section 2.2.3.3).
Message Properties: A collection of implementation-specific, name-value pairs that are transmitted as part of a Remote Method invocation. Message Properties are used to exchange implementation-specific data between clients and servers.
method signature: A list of the remoting types of the arguments of a remote method.
NT LAN Manager (NTLM) Authentication Protocol: A protocol using a challenge-response mechanism for authentication in which clients are able to verify their identities without sending a password to the server. It consists of three messages, commonly referred to as Type 1 (negotiation), Type 2 (challenge) and Type 3 (authentication).
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.
One-Way Method: A Remote Method that has no application response sent from the implementation of the Remote Method back to the caller. This pattern is sometimes referred to as "fire and forget".
Output Argument: A named 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).
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
Primitive Value: Part of the Remoting Data Model. A Primitive Value is an instance of a Primitive Type.
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 Data Model: A model that is used to represent higher-layer–defined data structures and values, and to represent a Remote Method invocation and the Return Value or error information from that invocation. A protocol, such as [MS-NRLS], that is built on top of this protocol can be defined by using the Remoting Data Model, and can be agnostic to the serialization format. For more information, see Abstract Data Model (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
Request URI: A URI that provides an address of a Server Object. The Request URI has two major components: a component that is used by the underlying transport to route the message to an appropriate transport endpoint (Channel URI); and another component to map the message to a Server Object within a server (Server Object URI).
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).
serialization: A mechanism by which an application converts an object into an XML representation.
Serialization Format: The structure of the serialized message content, which can be either binary or SOAP. Binary serialization format is specified in [MS-NRBF]. SOAP serialization format is specified in [MS-NRTP].
serialize: The process of taking an in-memory data structure, flat or otherwise, and turning it into a flat stream of bytes. See also marshal.
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.
Simple and Protected GSS-API Negotiation Mechanism (SPNEGO): An authentication mechanism that allows Generic Security Services (GSS) peers to determine whether their credentials support a common set of GSS-API security mechanisms, to negotiate different options within a given security mechanism or different options from several security mechanisms, to select a service, and to establish a security context among themselves using that service. SPNEGO is specified in [RFC4178].
Single-Call SAO: An SAO that is created every time a Remote Method on its Server Type is called. For longer-lived SAOs, see Singleton SAO.
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.
SOAP: A lightweight protocol for exchanging structured information in a decentralized, distributed environment. SOAP uses XML technologies to define an extensible messaging framework, which provides a message construct that can be exchanged over a variety of underlying protocols. The framework has been designed to be independent of any particular programming model and other implementation-specific semantics. SOAP 1.2 supersedes SOAP 1.1. See [SOAP1.2-1/2003].
SOAP Format Identifier: A string that is contained in the message frame. It identifies the serialization format of the message content as specified in [SOAP1.1]. Its value is 'text/xml; charset="utf-8"'.
System Library: A specially designated library that can be used to reduce the wire size for commonly used data types. The name of the library is agreed to by both the server and the client.
System.Object: Part of the Remoting Data Model. System.Object is a Class that has no Members. A Class that does not extend another Class is considered to extend System.Object.
Transmission Control Protocol (TCP): A protocol used with the Internet Protocol (IP) to send data in the form of message units between computers over the Internet. TCP handles keeping track of the individual units of data (called packets) that a message is divided into for efficient routing through the Internet.
Two-Way Method: A Remote Method that has a response sent from the implementation of the Remote Method back to the caller.
Unicode: A character encoding standard developed by the Unicode Consortium that represents almost all of the written languages of the world. The Unicode standard [UNICODE5.0.0/2007] provides three forms (UTF-8, UTF-16, and UTF-32) and seven schemes (UTF-8, UTF-16, UTF-16 BE, UTF-16 LE, UTF-32, UTF-32 LE, and UTF-32 BE).
Uniform Resource Identifier (URI): A string that identifies a resource. The URI is an addressing mechanism defined in Internet Engineering Task Force (IETF) Uniform Resource Identifier (URI): Generic Syntax [RFC3986].
user agent: An HTTP user agent, as specified in [RFC2616].
UTF-8: A byte-oriented standard for encoding Unicode characters, defined in the Unicode standard. Unless specified otherwise, this term refers to the UTF-8 encoding form specified in [UNICODE5.0.0/2007] section 3.9.
XML: The Extensible Markup Language, as described in [XML1.0].
XML namespace: A collection of names that is used to identify elements, types, and attributes in XML documents identified in a URI reference [RFC3986]. A combination of XML namespace and local name allows XML documents to use elements, types, and attributes that have the same names but come from different sources. For more information, see [XMLNS-2ED].
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.