mirror of
https://github.com/urbit/shrub.git
synced 2024-12-19 08:32:39 +03:00
03401b46aa
This brings it in line with the serialization found in /mar/noun. The `@uw`-encoding was carried over from Eyre, who uses it for channels. In that context, outgoing jam bytes must be encoded, because newline characters (`0a` bytes) would break up the SSE data field. Because they're essentially part of the same protocol, Eyre mirrors this for incoming nouns. Even though PUT requests can carry arbitrary bytes just fine, the symmetry and protocol-wide consistency seems important. Here, we are dealing strictly with plain HTTP requests, and strictly with requests that have indicated support for the `application/x-urb-jam` mime type to boot. We should have no qualms about raw jam bytes. They're more compact/efficient, too. |
||
|---|---|---|
| .. | ||
| arvo | ||
| autoprop | ||
| base-dev | ||
| herb | ||
| interface | ||
| landscape | ||
| symbolic-merge.sh | ||