Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
What's new
9
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Switch to GitLab Next
Sign in / Register
Toggle navigation
Open sidebar
yaq
yaq enhancement proposals
Commits
e0cf4b7d
Commit
e0cf4b7d
authored
Jan 15, 2021
by
Kyle Sunden
Browse files
Options
Browse Files
Download
Plain Diff
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
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
0 deletions
+5
-0
yeps/yep-103.md
yeps/yep-103.md
+5
-0
No files found.
yeps/yep-103.md
View file @
e0cf4b7d
...
...
@@ -6,6 +6,7 @@ status: accepted
tags
:
standard
post-history
:
2020-04-14
2020-07-02
2021-01-15
---
# Abstract
...
...
@@ -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.
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
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment