Mitar

Sure, but how would you know for strings if field has been provided and is empty string vs. it has not been provided at all?

I mean, I completely agree that those pointers seem to be more or less unnecessary, in almost all cases. And pain to work with. But then I also hate when...

So language should be: ``` If a client requests "Subscribe: keep-alive", then the subscription CAN be remembered even after the GET connection closes. A subscription CAN be resumed by the...

Why shouldn't braid patches be cached? They are cached given the version, no? We should just make ETag == Version.

Interesting fact about ETags, but not sure if it matters. I am realizing it does not really help with the fact that a new client still gets wrong contents, in...

Oh, I missed that. That is a different design decision that what I was thinking/expecting, so maybe I skipped over that. Hm, I would love to understand why you would...

I am continuing the discussion from above. That we should use two different content types for state vs. patch. And that for patch we have a default content type we...

After more investigation here, you are right, when using range-requests you use same content-type as the full content is. And in that case partial content status code should be used...

I think we can use [Vary header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Vary) and require Braid HTTP client to always list `Version` and `Parents` there?

I suggest that `Subscribe` should include maybe also the version of the protocol or subscription support. Or maybe list support for different transport protocols if we ever want to support...