@@ -76,8 +76,8 @@ So far, all the paths specified have been GET requests. Authentication, however,
76- `POST {oryx,ship?} /~/auth.json?DELETE` revokes authorization. Response as above.
76- `POST {oryx,ship?} /~/auth.json?DELETE` revokes authorization. Response as above.
78## 1.4 Messaging
78## 1.4 Messaging
79−- `POST {oryx, xyro} /~/to/[app]/[mark].json`, where `xyro` is data that will be converted to the `mark`. In the simplest case, `/~/do/hello/json.json` will pass `xyro` through verbatim, sending `[%json xyro]` to the `++poke` arm of app `%hello`.
79+- `POST {oryx, wire, xyro} /~/to/[app]/[mark].json`, where `xyro` is data that will be converted to the `mark`. In the simplest case, `/~/to/hello/json.json` will pass `xyro` through verbatim, sending `[%json xyro]` to the `++poke` arm of app `%hello`.
80−- `POST {oryx, xyro} /~/to/<ship>/[app]/[mark].json` is a foreign message send, as above.
80+- `POST {oryx, wire, xyro} /~/to/<ship>/[app]/[mark].json` is a foreign message send, as above.
82## 1.5 Subscriptions <a id="subs"/>
82## 1.5 Subscriptions <a id="subs"/>
83- `/~/of/[ixor]`<a id="of-ixor"/> is an `EventSource`: a conceptually infinite file containing a stream of events. By default, it sends a newline every 30 seconds serving to signal that the connection is alive to both the server and IP middleware.
83- `/~/of/[ixor]`<a id="of-ixor"/> is an `EventSource`: a conceptually infinite file containing a stream of events. By default, it sends a newline every 30 seconds serving to signal that the connection is alive to both the server and IP middleware.
@@ -130,9 +130,13 @@ Userspace http request, converted by `%ford` into an actual `hiss`.
130The primary `%eyre` request type comes from the host system, and constitutes an inbound http request. It consists of five parts:
130The primary `%eyre` request type comes from the host system, and constitutes an inbound http request. It consists of five parts:
132I. `p=[? @if]`: a loobean determining whether the request is being made over https, and the client source, an IPv6 address possibly encoding an IPv4 one as `.0.0.0.0.0.ffff.wwxx.yyzz`
132I. `p=[? @if]`: a loobean determining whether the request is being made over https, and the client source, an IPv6 address possibly encoding an IPv4 one as `.0.0.0.0.0.ffff.wwxx.yyzz`
133II. `q=meth`, an http method
134II. `q=meth`, an http method
134III. `r=@t`, the unparsed URL
136III. `r=@t`, the unparsed URL
135IV. `s=mess`, an associative list of header keys/values
138IV. `s=mess`, an associative list of header keys/values
136V. `t=(unit octs)`, the request body, if any.
140V. `t=(unit octs)`, the request body, if any.
138After `r` is parsed to a `purl`, the `pork`(relative path) determines the resource being served. The first step in handling an http request is [classifying its intent](#perk).
142After `r` is parsed to a `purl`, the `pork`(relative path) determines the resource being served. The first step in handling an http request is [classifying its intent](#perk).
@@ -353,9 +357,12 @@ Each `oryx` has active subscription state.
353- An `oryx` is a CSRF token used for [authenticated requests](#auth)
357- An `oryx` is a CSRF token used for [authenticated requests](#auth)
354- `mean.json`<a id="mean-json"/> is a rendering of hoon `ares`: an error message formatted as `{fail:'type',mess:"Error message"}`
358- `mean.json`<a id="mean-json"/> is a rendering of hoon `ares`: an error message formatted as `{fail:'type',mess:"Error message"}`
355- `urb.js`<a id="urb-js"/> is the standard client-side implementation of the `%eyre` protocols, normally found in `/=main=/lib`
359- `urb.js`<a id="urb-js"/> is the standard client-side implementation of the `%eyre` protocols, normally found in `/=main=/lib`
356−- The act of "serving" \<a id="mime"/>, refers to the wrapping of a `%mime` cage in an HTTP `200 Success` response, and errors or other marks being [sent to ford](#done) for conversion. Inside a `sign`, this conversion occurs along the same [`wire`](#wire); otherwise, the `wire` is [empty](#wire-drop).
360+- The act of "serving"<a id="mime"/>, refers to the wrapping of a `%mime` cage in an HTTP `200 Success` response, and errors or other marks being [sent to ford](#done) for conversion. Inside a `sign`, this conversion occurs along the same [`wire`](#wire); otherwise, the `wire` is [empty](#wire-drop).
358# Appendix B: EventSource <a id="eventsource"/>
362# Appendix B: EventSource <a id="eventsource"/>
359For more information, see <http://dev.w3.org/html5/eventsource/>
366For more information, see <http://dev.w3.org/html5/eventsource/>
361An EventSource is a stream of events, encoded in a conceptually infinite `GET` request. Each event is formatted as
368An EventSource is a stream of events, encoded in a conceptually infinite `GET` request. Each event is formatted as