wicrum-wicrun/sss
1
1
Fork 0
mirror of https://github.com/wicrum-wicrun/sss.git synced 2024-09-11 18:37:26 +03:00
Code Issues Packages Projects Releases Wiki Activity

Remove mentions of +on-wave

Browse Source
This commit is contained in:
~wicrum-wicrun 2022-12-05 02:56:35 +01:00
parent 75e456c273
commit 2d5a939a0c
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@ -204,10 +204,10 @@ your agent!
### State replication
So far, the subscriber has only had access to the replicated state in the
`+on-wave` and `+on-rock` arms, and the publisher has never had access to it.
State is supposed to be always available, so this is clearly insufficient. We
solve this by putting two maps containing all the incoming and outgoing states
in the agent's sample:
`+on-rock` arm, and the publisher has never had access to it. State is supposed
to be always available, so this is clearly insufficient. We solve this by
putting two maps containing all the incoming and outgoing states in the agent's
sample:
```hoon
^- agent:sss
@ -244,7 +244,7 @@ interface declaration by changing the terminator from `~` to `*`:
This would enable the agent to subscribe to `/chats`, `/chats/chat-1`,
`/chats/chat-2`, `/chats/chat-1/subchat-1` and so on. These would all be handled
using the same `$lake` interface, but would still appear as completely distinct
states in `+on-rock`, `+on-wave` and in the `map` in the agent's sample.
states in `+on-rock` and in the `map` in the agent's sample.
## Evolution of SSS
...