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.
binary large object (BLOB): A discrete packet of data that is stored in a database and is treated as a sequence of uninterpreted bytes.
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].
DSLR: Device Services Lightweight Remoting Protocol, as specified in [MS-DSLR]. A COM-like protocol that enables remoting of services, such as function calls and events, over a reliable point-to-point connection.
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).
host: A general-purpose computer that is networking capable.
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.
little-endian: Multiple-byte values that are byte-ordered with the least significant byte stored in the memory location with the lowest address.
message: A data structure representing a unit of data transfer between distributed applications. A message has message properties, which may include message header properties, a message body property, and message trailer properties.
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.
protected content: Any content or information, such as a file, Internet message, or other object type, to which a rights-management usage policy is assigned and is encrypted according to that policy. See also Information Rights Management (IRM).
proximity detection: The procedure in which a transmitter determines if a receiver is near.
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.
receiver: The node that is the receiver of the protocol stream.
server: An entity that transfers content to a client through streaming. A server might be able to do streaming on behalf of another server; thus, a server can also be a proxy. See [MS-WMLOG]
service: A SIP method defined by Session Initiation Protocol Extensions used by the client to request a service from the server.
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.
transmitter: A device that issues policy and transfers content to a receiver. An example of a transmitter is a digital media server.
WMDRM-ND: Windows Media Digital Rights Management for Network Devices. A protocol in the digital rights management (DRM) system that extends the reach of protected content to consumer electronic devices (such as digital media receivers) that are connected to transmitting devices (such as personal computers) over home Internet protocol (IP) networks.
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.