@ccmsg/protocol 0.5.0 → 0.5.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/src/messaging/direct-delivery.ts +8 -3
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ccmsg/protocol",
3
- "version": "0.5.0",
3
+ "version": "0.5.1",
4
4
  "description": "Wire contract (schema + types + op attribute table) shared by the ccmsg daemon and web UI",
5
5
  "license": "MIT",
6
6
  "author": "kawaz",
package/src/messaging/direct-delivery.ts CHANGED
@@ -23,9 +23,14 @@ export const DIRECT_DELIVERY_TAG = "cross-session-message";
23
23
  *
24
24
  * Not the sender's session and not a `uds:` path. Those are the addresses the
25
25
  * harness itself dials, and dialing one that has gone ends the recipient's turn
26
- * in failure; the sender here is a daemon that offers no such socket anyway.
27
- * A name asks for no answer, so there is nothing to dangle — the way back is
28
- * the reply line, which the recipient runs rather than the harness. */
26
+ * in failure. A name asks for no answer, so there is nothing to dangle — the
27
+ * way back is the reply line, which the recipient runs rather than the harness.
28
+ *
29
+ * The frame this wrapper is written in is a separate address: there the
30
+ * instance may name a `uds:` socket of its own, which is where the receiving
31
+ * harness writes what became of the delivery. Those receipts are negative only
32
+ * — `refused`, `denied`, `dropped`, `expired`, `held` — so silence within the
33
+ * window is what says the message was taken. */
29
34
  export const DIRECT_DELIVERY_FROM = "ccmsg";
30
35
 
31
36
  /** What the recipient is told the sender is doing. `prompting` is what a peer