Braid: Synchronization for HTTP
Reading the RFC, this seems to make HTTP stateful:<p>"A subscription is different from a GET connection (e.g. a TCP connection, or HTTP/2 stream).  If a client requests "Subscribe: keep-alive", then the subscription will be remembered even after the GET connection closes."<p>It also uses PUT to patch things, but then why not use PATCH ? You could say it's non standard, but at this point, everybody uses it. Plus their stuff apparently deviates from the HTTP standard as well by allowing headers after the first line of the payload and introducing the forGET command.<p>Or am I missing something ?<p>Interesting anyway, especially the way they create of graph of unique ID to solve the ordering problem. Feels like Git. The flow of patch reminds me of react-redux.<p>Plus it's great to have more geeky technical things on HN. I'm missing it, among all the news and start up things.<p>They also mention a really cool RFC on a JSON patch format: <a href="https://datatracker.ietf.org/doc/html/rfc6902" rel="nofollow">https://datatracker.ietf.org/doc/html/rfc6902</a><p>I'm reading RFC and getting excited about it. Damn, that must be what they call growing old.