Mitar

I think 410 Gone is almost perfect for this: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/410 Or maybe simply 404?

Maybe something in the transport for the subscription can be used? In SSE, different event types could be used, one for creation event, one for deletion, and one for change.

Hm, isn't deletion just a patch which removes everything? :-) So maybe just a patch-language should be rich enough to differentiate between change to "empty data" vs. "remove data itself".

There might be also another operation, i.e., `REDACT`, where maybe you are unable to publish anymore the patch (e.g., for legal reasons) but you can still provide metadata so that...

PUT should never be catched. In any case, [post/redirect/get](https://en.wikipedia.org/wiki/Post/Redirect/Get) could be used here, too (just put instead).

So do redirect always as response to PUT. :-)

See also: https://stackoverflow.com/questions/626057/is-it-possible-to-cache-post-methods-in-http So interesting is that PUT also invalidates the cache of GET for same URI.

OK, just to be clear, HTTP2 PUSH does not allow server to send data to the client for which the client is not aware of (e.g., a message of type...

> The client will want to fetch the list of messages, and then each message within, but it won't know the URLs of each inner message until it fetches the...

Yea, if you want to pull just a subset of fields from the related object. For example, a Linked JSON of: ``` { "foo": {"link": "http://example.com/foo#json=/field1,/field2"} } ``` That would...