From 6a5dd69f86f4a082c5a4677d4c0258eb26344fb0 Mon Sep 17 00:00:00 2001 From: Rob Austin Date: Mon, 20 Oct 2014 18:33:38 +0100 Subject: [PATCH] HCOLL-167 improved readme added --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 3bb70f361..e0a363009 100644 --- a/README.md +++ b/README.md @@ -621,7 +621,8 @@ replicator.close(); 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. + 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. ``` java // server