|
Pool User
A Pool User (PU) is a client in the Reliable Server Pooling (RSerPool) framework. In order to use the service provided by a pool, a PU has to proceed the following steps: * Ask a Pool Registrar for server selection (the Pool Registrar will return a list of servers, called Pool Elements), * Select one Pool Element, establish a connection and use the actual service, * Repeat the server selection and connection establishment procedure in case of server failures, * Perform an application-specific session failover to a new server to resume an interrupted session, * Report failed servers to the Pool Registrar In computing, a Pool Registrar (PR) is a component of the reliable server pooling (RSerPool) framework which manages a handlespace. PRs are also denoted as ENRP server or Name Server (NS). The responsibilities of a PR are the following: * Register .... Standards Documents Aggregate Server Access Protocol (ASAP)Endpoint Handlespace Redundancy Protocol (ENRP)Aggregate Server Acces ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Client (computing)
In computing, a client is a piece of computer hardware or software that accesses a service made available by a server as part of the client–server model of computer networks. The server is often (but not always) on another computer system, in which case the client accesses the service by way of a network. A client is a computer or a program that, as part of its operation, relies on sending a request to another program or a computer hardware or software that accesses a service made available by a server (which may or may not be located on another computer). For example, web browsers are clients that connect to web servers and retrieve web pages for display. Email clients retrieve email from mail servers. Online chat uses a variety of clients, which vary on the chat protocol being used. Multiplayer video games or online video games may run as a client on each computer. The term "client" may also be applied to computers or devices that run the client software or users that use th ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Reliable Server Pooling
Reliable Server Pooling (RSerPool) is a computer protocol framework for management of and access to multiple, coordinated (pooled) servers. RSerPool is an IETF standard, which has been developed by the IETF RSerPool Working Group and documented in RFC 5351, RFC 5352, RFC 5353, RFC 5354, RFC 5355 and RFC 5356. Introduction In the terminology of RSerPool a server is denoted as a Pool Element (PE). In its Pool, it is identified by its Pool Element Identifier (PE ID), a 32-bit number. The PE ID is randomly chosen upon a PE's registration to its pool. The set of all pools is denoted as the Handlespace. In older literature, it may be denoted as Namespace. This denomination has been dropped in order to avoid confusion with the Domain Name System (DNS). Each pool in a handlespace is identified by a unique Pool Handle (PH), which is represented by an arbitrary byte vector. Usually, this is an ASCII or Unicode name of the pool, e.g. "DownloadPool" or "WebServerPool". Each handlespace ha ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Pool Registrar
In computing, a Pool Registrar (PR) is a component of the reliable server pooling (RSerPool) framework which manages a handlespace. PRs are also denoted as ENRP server or Name Server (NS). The responsibilities of a PR are the following: * Register Pool Elements into a handlespace, * Deregister Pool Elements from a handlespace, * Monitor Pool Elements by keep-alive messages, * Provide handle resolution (i.e. server selection) to Pool User A Pool User (PU) is a client in the Reliable Server Pooling (RSerPool) framework. In order to use the service provided by a pool, a PU has to proceed the following steps: * Ask a Pool Registrar for server selection (the Pool Registrar will return ...s, * Audit the consistency of a handlespace between multiple PRs, * Synchronize a handlespace with another PR. Standards Documents Aggregate Server Access Protocol (ASAP)Endpoint Handlespace Redundancy Protocol (ENRP)Aggregate Server Access Protocol (ASAP) and Endpoint Handlespace Redundancy Pr ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Internet Protocols
The Internet protocol suite, commonly known as TCP/IP, is a framework for organizing the set of communication protocols used in the Internet and similar computer networks according to functional criteria. The foundational protocols in the suite are the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and the Internet Protocol (IP). In the development of this networking model, early versions of it were known as the Department of Defense (DoD) model because the research and development were funded by the United States Department of Defense through DARPA. The Internet protocol suite provides end-to-end data communication specifying how data should be packetized, addressed, transmitted, routed, and received. This functionality is organized into four abstraction layers, which classify all related protocols according to each protocol's scope of networking. An implementation of the layers for a particular application forms a protocol stack. From lowest to high ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
