Publish pubsub messages over Iroh
This commit is contained in:
parent
f85039367c
commit
e294965833
8 changed files with 357 additions and 28 deletions
|
|
@ -158,8 +158,12 @@ Automerge CRDT state. Automerge state encoding and sync are future work.
|
|||
`geth-pubsub` currently supports local publish/subscribe snapshots through the
|
||||
daemon control protocol. Messages live in a bounded in-memory ring buffer and
|
||||
are lost when the daemon stops. This is deliberate: pubsub is a lossy wakeup and
|
||||
presence channel, not authoritative storage. Iroh-gossip replication, private
|
||||
topics, and capability enforcement are future work.
|
||||
presence channel, not authoritative storage. `geth pubsub pub <topic> <message>
|
||||
--node <node-id>` can publish to an imported peer over the protected Iroh
|
||||
control ALPN. The remote daemon validates endpoint/card binding and requires
|
||||
`pubsub.publish` on `resource:pubsub:<topic>` before recording the message in
|
||||
its local ring buffer. Iroh-gossip replication and private topics are future
|
||||
work.
|
||||
|
||||
`geth-pipe` currently supports `pipe listen/connect` against a local
|
||||
daemon-lifetime registry. This is a control-plane scaffold for names and
|
||||
|
|
|
|||
Loading…
Reference in a new issue