Commit e0cf4b7d authored by Kyle Sunden's avatar Kyle Sunden
Browse files

Merge branch 'clarify-purpose-of-state' into 'master'

clarify the purpose of the state file

See merge request !57
parents ab712b38 9b41b703
Pipeline #242268772 passed with stage
in 48 seconds
...@@ -6,6 +6,7 @@ status: accepted ...@@ -6,6 +6,7 @@ status: accepted
tags: standard tags: standard
post-history: 2020-04-14 post-history: 2020-04-14
2020-07-02 2020-07-02
2021-01-15
--- ---
# Abstract # Abstract
...@@ -35,6 +36,10 @@ Defaults are specified in the daemon's [protocol](../107). ...@@ -35,6 +36,10 @@ Defaults are specified in the daemon's [protocol](../107).
When reasonable defaults are not possible, Daemons SHOULD return Error states over [RPC](../107) calls for calls which require state information. When reasonable defaults are not possible, Daemons SHOULD return Error states over [RPC](../107) calls for calls which require state information.
A missing file MUST NOT cause the daemon to fail to start up and accept client connections. A missing file MUST NOT cause the daemon to fail to start up and accept client connections.
Becuase yaq uses a simple text file to store state, it's not reccomended to treat the state file as an active datastore.
Daemons SHOULD use the state file as a periodically-written backup.
Active state information will typically be kept in-memory.
In most cases, the content of a state file will only be read by the daemon at startup.
## File Location ## File Location
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment