> this seems to make HTTP stateful Yes -- depending on how you look at it. HTTP already has cookies to implement stateful sessions. Braid does add subscripti

> this seems to make HTTP stateful Yes -- depending on how you look at it. HTTP already has cookies to implement stateful sessions. Braid does add subscriptions; but HTTP 1.1 and 2 also has keep-alive at the TCP level: https://en.wikipedia.org/wiki/HTTP_persistent_connection https://en.wikipedia.org/wiki/HTTP_persistent_connection > It also uses PUT to patch things, but then why not use PATCH? You can use PATCH, or even POST, too. We haven't settled on a single best method to use, and in fact you'll notice different methods being used in different specs, depending on the personal preferences of the author that wrote that spec. :) I recommend checking out the Range Patch spec for more: https://datatracker.ietf.org/doc/html/draft-toomim-httpbis-range-patch-00 https://datatracker.ietf.org/doc/html/draft-toomim-httpbis-r.... You'll see a lot of PATCH in there. :) Also, please feel free to start a discussion on the mailing list about this: ietf-http-wg@w3.org It's an issue that needs discussion and consensus more generally in HTTP.