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

Replace term Chronicle Map instance with Chronicle Map [data|key-value] store in specification, to reduce confusion

Browse Source
This commit is contained in:
leventov
2016-03-23 20:30:37 +07:00
parent 739796b90d
commit 8c4a5ef71b
8 changed files with 32 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files
spec/README.md
+1 -1
View File
@@ -21,7 +21,7 @@ This is currently work-in-progress.
- To provide the ability to write a Chronicle Map implementation in a non-JVM language e.g. C, C++,
C#, or Go. As Chronicle Map is designed for concurrent inter-process access, performance-critical
operations on a Chronicle Map instance could be done from a C++ process, while a concurrent process
operations on a Chronicle Map store could be done from a C++ process, while a concurrent process
running the Java implementation is doing some duty tasks such as backup to a rational database.
- This specification is the source of truth to reason about the Chronicle Map data store behaviour