> The reasoning behind this seems to be that the alternatives right now are either polling or a homegrown websocket based protocol. Right. Same with routed RPC

> The reasoning behind this seems to be that the alternatives right now are either polling or a homegrown websocket based protocol. Right. Same with routed RPC and routed PUB/SUB. I currently use the WAMP (protocol, not stack) for that, as it is a Webocket based IANA standard, but with http2/3, having the HTTP version of it would make sense to have this baked in as well. In fact, their subscribe thingy should probably be more generic and accept a topic and optional params. Params could be then use to upgrade the use case, like version+parents for sync. Plus client may want to push events as well. I don't know how one can contribute to the debate. Would you explain it to me? > I've personally seen both PUT and PATCH used for updates, so this didn't seem particularly odd to me, and seemed more like a nod to one particular method of updates. PUT in REST is for sending the full object, PATCH is for partial updates. So both are valid, but I would allow the "Patches" headers for the PATCH method only.