1.1 Glossary
This document uses the following terms:
big-endian: Multiple-byte values that are byte-ordered with the most significant byte stored in the memory location with the lowest address.
Component Object Model (COM): An object-oriented programming model that defines how objects interact within a single process or between processes. In COM, clients have access to an object through interfaces implemented on the object. For more information, see [MS-DCOM].
consumer: A DSLR service implementer. The consumer defines the service functions, and implements the proxy on the client and the stub on the server.
dispatch event: A one-way event sent from the client to the server.
dispatch request: A two-way request made on the remote service. The service returns the result and out parameters for a dispatch request in the form of a dispatch response.
dispatch response: The response (result and out parameters) for a two-way DSLR request made on a remote service.
dispatcher: DSLR session layer. The dispatcher manages the set of transactions, or requests made on the remote service.
dispenser: DSLR application layer. The dispenser is a service that exposes locally implemented services to the remote endpoint, and allows for remote services to be instantiated. Manages the set of local services instantiated on the server.
globally unique identifier (GUID): A term used interchangeably with universally unique identifier (UUID) in Microsoft protocol technical documents (TDs). Interchanging the usage of these terms does not imply or require a specific algorithm or mechanism to generate the value. Specifically, the use of this term does not imply or require that the algorithms described in [RFC4122] or [C706] must be used for generating the GUID. See also universally unique identifier (UUID).
handle: Any token that can be used to identify and access an object such as a device, file, or a window.
HRESULT: An integer value that indicates the result or status of an operation. A particular HRESULT can have different meanings depending on the protocol using it. See [MS-ERREF] section 2.1 and specific protocol documents for further details.
interface: A specification in a Component Object Model (COM) server that describes how to access the methods of a class. For more information, see [MS-DCOM].
ISO/OSI reference model: The International Organization for Standardization Open Systems Interconnection (ISO/OSI) reference model is a layered architecture (plan) that standardizes levels of service and types of interaction for computers that are exchanging information through a communications network. Also called the OSI reference model.
network byte order: The order in which the bytes of a multiple-byte number are transmitted on a network, most significant byte first (in big-endian storage). This may or may not match the order in which numbers are normally stored in memory for a particular processor.
payload: Tag-specific data sent as part of each DSLR message ([MS-DSLR]). Each DSLR tag contains one payload. Examples include Dispatcher Request tag payload ([MS-DSLR] section 2.2.2.1) (data identifying the type of request being made on the remote service), dispenser CreateService message payload ([MS-DSLR] section 2.2.2.3) (the parameters for the CreateService function), service-specific function payloads (the parameters for the service-specific functions), and so on.
proxy: A network node that accepts network traffic originating from one network agent and transmits it to another network agent.
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.
stub: Used as specified in [C706] section 2.1.2.2. A stub that is used on the client is called a "client stub", and a stub that is used on the server is called a "server stub".
tag: The format of all Device Services Lightweight Remoting Protocol ([MS-DSLR]) messages includes the size of the payload, number of children, and the tag payload itself.
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.