Ikarus/libikarus
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

a new beginning

Browse source 
Signed-off-by: Folling <mail@folling.io>
This commit is contained in:
Folling 2023-08-22 00:27:22 +02:00 • committed by Folling
commit ca4d4a5dbe
No known key found for this signature in database
25 changed files with 1718 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

11
README.md Normal file
View file

@ -0,0 +1,11 @@
### Data Longevity
All data returned by libikarus is ephemeral and only represents the state of the project at the time of the request.
A snapshot if you will.
One must not rely on it representing the actual state of the project at any given time. The data is simply copied
from the underlying data sources and returned to the caller.
No mechanisms are provided to avoid race conditions. LibIkarus itself should only be used in a single-threaded context.
However, nothing breaks if you do use it in a multithreaded context, that is, libikarus is threadsafe.
You just cannot rely on the data being consistent.
This goes especially for inter-process access to the same project.