anchor.diff:  ## system member
   
   A process that has established a connection to a distributed system.
  +
  +<a id="nc_glossary_time-to-live"></a>
   
   ## time-to-live
   
  
positive.code: 
  Document Type Definition. A language that describes the contents of a Standard Generalized Markup Language (SGML) document. The DTD is also used with XML. The DTD definitions can be embedded within an XML document or in a separate file.
  
  ## entry
  
  A data object in a region. A region entry consists of a key and a value. The value is either null (invalid) or an object. A region entry knows what region it is in. See also **region data**, **entry key**, and **entry value**.
  
  ## entry key
  
  The unique identifier for an entry in a region.
  
  ## entry value
  
  The data contained in an entry.
  
negative.code: 
  Applications and cache servers connect to a <span class="keyword">Geode</span> distributed system by invoking the static function `DistributedSystem::connect`. Through this connection, the application gains access to the APIs for distributed data caches. When a C++ or .NET application connects to a distributed system, it specifies the system it is connecting to by indicating the communication protocol and address to use to find other system members.
  
  <a id="nc_glossary_netSearch"></a>
  
  ## netSearch
  
  The method used by <span class="keyword">Geode</span> to search remote caches for a data entry that is not found in the local cache region. This operates only on distributed regions.
  
  <a id="nc_glossary_overflows"></a>
  
  ## overflows
  
  An eviction option that causes the values of LRU entries to be moved to disk when the region reaches capacity. See [disk policy](#nc_glossary_disk_policy).
  
  ## persistence manager
  
  The persistence manager manages the memory-to-disk and disk-to-memory actions for LRU entries. See [overflows](#nc_glossary_overflows).
  
  ## region
  
  A logical grouping of data within a cache. Regions are used to store data entries (see [entry](#nc_glossary_entry)). Each region has a set of attributes governing activities such as expiration, distribution, data loading, events, and eviction control.
  
  ## region attributes
  
  The class of attributes governing the creation, location, distribution, and management of a region and its entries.
  
  <a id="nc_glossary_region_data"></a>
  
  ## region data
  
  All of the entries directly contained in the region.
  
  ## region entry
  
  See [entry](#nc_glossary_entry).
  
  <a id="nc_glossary_remote_cache"></a>
  
  ## remote cache
  
  Any part of the distributed cache that is resident in a process other than the current one. If an application or cache server does not have a data entry in the region in its local cache, it can do a `netSearch` in an attempt to retrieve the entry from the region in a remote cache. See also [local cache](#nc_glossary_local_cache).
  
  <a id="nc_glossary_scope"></a>
  
  ## scope
  
  Region attribute. Identifies whether a region keeps its entries private or automatically sends entry value updates to remote caches and incorporates updates received from remote caches. The scope also identifies whether distribution operations must wait for acknowledgement from other caches before continuing. See also [distributed scope](#nc_glossary_distributed_scope) and [local scope](#nc_glossary_local_scope).
  
  ## serialization
  
  The process of converting an object graph to a stream of bytes.
  
  <a id="nc_glossary_server"></a>
  
  ## server
  
  In a client-server topology, the server manages membership and allows remote operations. The server maintains membership information for its clients in the distributed system, along with information about peer applications and other servers in the system. See also **cache server**.
  