braid-spec
braid-spec copied to clipboard
braid-org
Working area for Braid extensions to HTTP
Our current implementations (both `braidify` and `braid-protocol`) both set the `cache-control: no-cache, no-transform` header, but it looks like this is no longer in the spec. It looks like it used...
Some browsers (Firefox) will automatically close HTTP connections which have no data sent on them after 1 minute. It feels a little messy, but we should specify a heartbeat message...
This would be a pretty big update to the document, perhaps most appropriate as another document entirely. But I think it would be useful for servers to be able to...
In existing HTTP, if a resource doesn't exist, the server responds with a `404 not found` and ends the connection. A resource that exists can be deleted with the `DELETE`...
If a client does: 1. `GET` /foo subscribe 2. `PUT` /foo "hello" Then a naive server might send the client's PUT (2) back to it, because it subscribed in (1)....
After PR #93 is merged, we'll have changed the "Subscribe" header from 3 variants: ``` Subscribe or Subscribe: keep-alive or Subscribe: keep-alive= ``` to a single variant: ``` Subscribe ```...
This issue is a follow-up to #90 . The spec is now intentionally ambiguous about which error code to send when historical versions are missing or unavailable on the server....
NOTE: This is not asking to change the header "Version:" to something else, merely the concept relating to the "Version:" header. I want to elevate the discussion [here](https://github.com/josephg/braid-protocol/pull/7) to a...
NOTE: We're currently discussing changing "Content-Length" to "Patch-Length" in #97 so to be clear: This issue relates to "Patch-Length" if we decide to adopt that header name. Thanks to @toomim...
It'd be nice for a server to advertise that it lets you Subscribe to a resource. I'm thinking it could send in its response something like `Accepts:` or `Allow:`, except...