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-163 renamed chronicle custer to chronicle channel

Browse Source
This commit is contained in:
Rob Austin
2014-10-13 18:25:12 +01:00
parent 200322d268
commit abcd89ec5e
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+1 -1
View File
@@ -520,7 +520,7 @@ example of just two servers, they only have to be connected via a single tcp soc
the data is transferred both ways. Which is great, however what if you wanted to replicate more than
just one chronicle map, what if you were going to replicate two chronicle maps across your network,
unfortunately with just TCP replication you would have to have two tcp socket connections, which is
not ideal. This is why we created Chronicle Clustering. Clustering lets you replicate numerous
not ideal. This is why we created Chronicle Channels. Channels lets you replicate numerous
Chronicle Maps via a single point to point socket connection.
Chronicle Channels are similar to TCP replication, where each map has to be given a unique identifier, but