Mitar

I reread this again and I realized that this issue is really just about optimizing that client's own action does not come back to client itself over a subscription. It...

So the idea is that you should know that server supports different and which range units.

I mean, that comes from our work on the spec. We are extending range header to non-GET requests. it is important for the server to communicate that it supports that....

Related: https://github.com/braid-work/braid-spec/issues/49 And I completely agree.

> The problem of course is that this would break existing caches - which would see a GET then a 4xx response and invalidate their cache of the document contents....

Great point!

Maybe we could use `changeset` for a set of patches, and `version` for ID of the `changeset`.

Also, any range unit should also make sure it supports: #45

I think the idea of this issue is to introduce a new range unit name (you renamed the issue, so it is slightly confusing now).

Shouldn't heartbeats be done at a transport level and not at braid level? E.g., if subscriptions are done using SSE, then you can use some `hearbeat` event type. If you...