mirror of
https://github.com/OpenHFT/Chronicle-Map.git
synced 2021-09-13 01:26:12 +00:00
HCOLL-167 improved readme
This commit is contained in:
@@ -620,16 +620,8 @@ replicator.close();
|
||||
#### Stateless Client
|
||||
|
||||
|
||||
stateless client is an instance of a ChronicleMap or a Set that does not hold any data locally,
|
||||
all the Map operations are
|
||||
delegated via a Remote Procedure Calls ( RPC ) to another {@link ChronicleMap} or {@link
|
||||
ChronicleSet} which we will refer to as the server. The server will hold all your data,
|
||||
the server can not it’s self be a stateless client. Your stateless client must be connected to
|
||||
the server via TCP/IP. The stateless client will delegate all your method calls to the remote
|
||||
server. The stateless client operations will block, in other words the stateless client will wait
|
||||
for the server to send a response before continuing to the next operation. The stateless client
|
||||
could be consider to be a ClientProxy to {@link ChronicleMap} or {@link ChronicleSet}
|
||||
running on another host.
|
||||
A stateless client is an instance of a ChronicleMap or a ChronicleSet that does not hold any data
|
||||
locally, all the Map operations are delegated via a Remote Procedure Calls ( RPC ) to another ChronicleMap or ChronicleSet which we will refer to as the server. The server will hold all your data, the server can not it’s self be a stateless client. Your stateless client must be connected to the server via TCP/IP. The stateless client will delegate all your method calls to the remote server. The stateless client operations will block, in other words the stateless client will wait for the server to send a response before continuing to the next operation. The stateless client could be consider to be a ClientProxy to ChronicleMap or ChronicleSet running on another host.
|
||||
|
||||
``` java
|
||||
// server
|
||||
|
||||
Reference in New Issue
Block a user