@@ -28,7 +28,7 @@ A `wind` is defined in `arvo.hoon` as:
31− $% [%pass p=path q=a]
31+ $% [%pass p=wire q=a]
32 [%slip p=a]
32 [%slip p=a]
33 [%give p=b]
33 [%give p=b]
@@ -38,7 +38,7 @@ Gall will not accept a `%slip`, so we can ignore that. A `card`, then, is one
41−[%pass path note]
41+[%pass wire note]
42[%give gift]
42[%give gift]
@@ -55,18 +55,13 @@ task, or what have you, to another agent or vane. A `%pass` card is a request
55your agent _initiates_. This is in contrast to a [`%give`](#give) card, which is
55your agent _initiates_. This is in contrast to a [`%give`](#give) card, which is
56sent in _response_ to another agent or vane.
56sent in _response_ to another agent or vane.
58−The type of the first field in a `%pass` card is a `path`. A `path` is just a
58+The type of the first field in a `%pass` card is a `wire`. A `wire` is just a
59list of `@ta`, with a syntax of `/foo/bar/baz`. When you `%pass` something to an
59list of `@ta`, with a syntax of `/foo/bar/baz`. When you `%pass` something to an
60−agent or vane, this field specifies the `wire` on which the response should
60+agent or vane, the response will come back on the `wire` you specify here. Your
61−arrive. A `wire` has the exact same type as a `path` (`/foo/bar/baz`), the
62−`wire`/`path` distinction is merely to differentiate their uses. When the agent
63−or vane responds to your request, your agent will see the `wire` as well as the
64−response itself. Your agent can then check the `wire` and maybe do different
61+agent can then check the `wire` and maybe do different things depending on its
65−things depending on its content. Both the
66−[`wire`](/docs/userspace/gall-guide/types#wire) and
62+content. The [`wire`](/docs/userspace/gall-guide/types#wire) type is covered in
67−[`path`](/docs/userspace/gall-guide/types#path) types are are covered in the
68−[types reference](/docs/userspace/gall-guide/types). We'll show how `wire`s are
63+the [types reference](/docs/userspace/gall-guide/types). We'll show how `wire`s
69−practically used later on.
64+are practically used later on.
71The type of the next field is a `note:agent:gall` (henceforth just `note`), which
66The type of the next field is a `note:agent:gall` (henceforth just `note`), which
72`lull.hoon` defines as:
67`lull.hoon` defines as:
@@ -103,7 +98,14 @@ A `task:agent:gall` (henceforth just `task`) is defined in `lull.hoon` as:
101+Note a few of these include a `path` field. The `path` type is exactly the same
102+as a `wire` - a list of `@ta` with a syntax of `/foo/bar/baz`. The reason for
103+the `wire`/`path` distinction is just to indicate their separate purposes. While
104+a `wire` is for _responses_, a `path` is for _requests_. The
105+[`path`](/docs/userspace/gall-guide/types#path) type is also covered in the
106+[types reference](/docs/userspace/gall-guide/types).
106−These can be divided into two categories:
108+The kinds of `task`s can be divided into two categories:
108#### Subscriptions
110#### Subscriptions