@@ -1,6 +1,6 @@
2title = "Appendix: Types"
2title = "Appendix: Types"
3−weight = 60
3+weight = 65
4template = "doc.html"
4template = "doc.html"
@@ -198,7 +198,11 @@ The type of a wire is formally defined as:
200So, a `wire` is just a [`path`](#path), type-wise they're exactly the same. The
200So, a `wire` is just a [`path`](#path), type-wise they're exactly the same. The
201−reason there's a separate `wire` type is just to differentiate their purpose. A `wire` is a path for responses to requests an agent initiates. If you subscribe to the `path` `/some/path` on another agent, you also specify `/some/wire`. Then, when that agent sends out updates to subscribers of `/some/path`, your agent receives them on `/some/wire`.
201+reason there's a separate `wire` type is just to differentiate their purpose. A
202+`wire` is a path for responses to requests an agent initiates. If you subscribe
203+to the `path` `/some/path` on another agent, you also specify `/some/wire`.
204+Then, when that agent sends out updates to subscribers of `/some/path`, your
205+agent receives them on `/some/wire`.
203The `wire` is specified in the second argument of a `%pass` `card`. It's used
207The `wire` is specified in the second argument of a `%pass` `card`. It's used
204for anything you can `%pass`, such as `%poke`s, `%watch`es, and `%arvo` notes.
208for anything you can `%pass`, such as `%poke`s, `%watch`es, and `%arvo` notes.