1.1 Glossary

This document uses the following terms:

little-endian: Multiple-byte values that are byte-ordered with the least significant byte stored in the memory location with the lowest address.

Multiple Active Result Sets (MARS): A feature in Microsoft SQL Server that allows applications to have more than one pending request per connection. For more information, see [MSDN-MARS].

peer: The entity on either end of an established SMP session.

receiver: The entity that is receiving information from its peer. Both client and server can be receivers.

recycle: A process in which SMP releases a Session object so that the session identifier (SID) in use is made available again for a new session.

sender: The entity that is sending information to its peer. Both client and server can be senders.

session: In Kerberos, an active communication channel established through Kerberos that also has an associated cryptographic key, message counters, and other state.

session identifier (SID): A unique value provided by the SID field of a SYN packet to each session established over an SMP connection.

Session object: An instance of SMP created by a SYN packet that corresponds to the SESSION ESTABLISHED state and is designated by a unique session identifier (SID).

Session variable: Members of a Session object instance that contain data to facilitate various SMP operations, such as messaging, event processing, and packet flow control.

Tabular Data Stream (TDS): An application-level protocol that is used by SQL Server to facilitate requests and responses between a database server and client as specified in [MS-TDS].

Virtual Interface Architecture (VIA): A high-speed interconnect that requires special hardware and drivers that are provided by third parties.

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.