Alawn/Chronicle-Map
1
0
Fork 0
mirror of https://github.com/OpenHFT/Chronicle-Map.git synced 2021-09-13 01:26:12 +00:00
Code Releases Activity

HCOLL-167 readme

Browse Source
This commit is contained in:
Rob Austin
2014-10-20 20:06:56 +01:00
parent 2fc61d7d14
commit 801ec1c35c
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+3 -3
View File
@@ -12,7 +12,7 @@ Replicate your Key Value Store across your network, with consistency, durability
#### Maven Artifact Download
```xml
<dependency>
<dependency>
<groupId>net.openhft</groupId>
<artifactId>chronicle-map</artifactId>
<version><!--replace with the latest version--></version>
@@ -621,9 +621,9 @@ replicator.close();
![](http://openhft.net/wp-content/uploads/2014/07/Chronicle-Map-remote-stateless-map_04_vB.jpg)
A stateless client is an instance of a ChronicleMap or a ChronicleSet that does not hold any data
A stateless client is an instance of a `ChronicleMap` or a ChronicleSet that does not hold any data
locally, all the Map or Set 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.
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.
Below is an example of how to configure a stateless client.