1.1 Glossary
This document uses the following terms:
American National Standards Institute (ANSI) character set: A character set defined by a code page approved by the American National Standards Institute (ANSI). The term "ANSI" as used to signify Windows code pages is a historical reference and a misnomer that persists in the Windows community. The source of this misnomer stems from the fact that the Windows code page 1252 was originally based on an ANSI draft, which became International Organization for Standardization (ISO) Standard 8859-1 [ISO/IEC-8859-1]. In Windows, the ANSI character set can be any of the following code pages: 1252, 1250, 1251, 1253, 1254, 1255, 1256, 1257, 1258, 874, 932, 936, 949, or 950. For example, "ANSI application" is usually a reference to a non-Unicode or code-page-based application. Therefore, "ANSI character set" is often misused to refer to one of the character sets defined by a Windows code page that can be used as an active system code page; for example, character sets defined by code page 1252 or character sets defined by code page 950. Windows is now based on Unicode, so the use of ANSI character sets is strongly discouraged unless they are used to interoperate with legacy applications or legacy data.
application-sharing session: A session that is established between two or more nodes that allows every node in the session to simultaneously view running applications that are hosted on a selected node. For example, one node might have an active document application that it would like to share with other nodes in the established session.
ASCII: The American Standard Code for Information Interchange (ASCII) is an 8-bit character-encoding scheme based on the English alphabet. ASCII codes represent text in computers, communications equipment, and other devices that work with text. ASCII refers to a single 8-bit ASCII character or an array of 8-bit ASCII characters with the high bit of each character set to zero.
distributed model: In the S20 protocol, a group of nodes where one node (the creator node) is responsible for creating an application-sharing session and other nodes are able to join that same session.
Generic Conference Control (GCC): A high-level protocol for passing conference control information during a conference between geographically dispersed computers. GCC provides a set of services for setting up and managing the conference. For example, it includes information such as who is currently in the roster and node authorization for conferencing primitives. Additionally, the GCC protocol is used by applications to coordinate independent use of the MCS channels. For more information about GCC, see [T124] section 6.
multicasting: The process by which data is transmitted over a network to multiple recipients simultaneously.
Multipoint Communication Service (MCS): A data transmission protocol and set of services defined by the ITU T.120 standard, specifically [T122] and [T125].
NetMeeting: A feature of Windows that uses the Microsoft NetMeeting Protocol. This feature allows for voice, video, application-sharing, and text conferencing between two or more parties via TCP/UDP networks.
object manager instance: An entity that coordinates object creation, deletion and synchronization between two or more nodes in an established session. There is only one object manager instance present in each node.
page control object: An object used in whiteboard processing which indicates various states of a whiteboard page.
page control workset: A workset dedicated to hold Page Control Objects.
protocol data unit (PDU): Information that is delivered as a unit among peer entities of a network and that can contain control information, address information, or data. For more information on remote procedure call (RPC)-specific PDUs, see [C706] section 12.
S20: A protocol that is used by Microsoft NetMeeting for application-sharing. The S20 protocol was originally known as Share v2.0.
share roster: A list that is built from a group of nodes on the same application-sharing session.
workset: An item that contains a group of related objects used to update nodes joining a domain.
workset group: The NetMeeting Object Manager (section 2.2.5) protocol contains three different workset groups as follows: The Object manager control workset group that contain various worksets utilized to control the creation, modification, and deletion of objects across various nodes. The Application loader workset group that contain various worksets used in loading/unloading application functions across nodes. And the Whiteboard workset group that is dedicated to sending and receiving whiteboard objects.
workset group ID: A predefined value assigned to each workset group. For NetMeeting Object Manager (section 2.2.5) these values are as follows: 0 is assigned to the Object Manager Control workset group. 1 is assigned to the Application Loader workset group and 2 is assigned to the Whiteboard workset group.
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.