CAM (content-addressable memory)
A netcard driver accesses CAM using a data field rather than a data address.
A long-term communication association between two clients on a network. Communication through a connection is expected to be reliable and error-free.
The context collection associated with one end of a connection. There is exactly one connection between two connection endpoints. Each connection endpoint is associated with exactly one address object, but an address object can be associated with several connection endpoints. A connection endpoint is identified by a connection endpoint identifier.
The execution state of a thread at any given moment:
· For a user-mode thread, the platform-dependent register state, kernel stack, TEB, and user stack in the address space of the process to which the thread belongs.
· For a kernel-mode thread, the platform-dependent register state and kernel stack.
Kernel-mode threads have neither a TEB nor a user-mode context, but they must have an associated process. See also process object.
Most Windows NT device drivers do not have a context in this sense. Unless a driver (such as an FSD) creates its own process and/or thread(s), it does not have its own stack space or register state. For each driver, the set of objects it owns and the IRPs that it can access in the device queue associated with its device object or any driver-created internal queue(s) can be considered all or part of its context.
A TDI client binding to a TDI driver. The client uses the control channel to query and set global information.
CRC (circular redundancy check)
A method of ensuring data integrity for transmissions over a network. The receiving node uses the CRC value in a packet for comparison with a value calculated by using the same algorithm the sender uses to calculate the original CRC value.
A type of signal used on a LocalTalk network.