# Braid Meeting 89

<a href="https://us02web.zoom.us/j/6459283736?pwd=cW1OcnlZQndXS3pKQ1U3K01NRHJZQT09"><span style="display: inline-block; padding: 0 4; background-color: #4078C0; color: white; font-weight: 400; border-radius: 4px;">Meet in Zoom</span></a> on Monday, July 8 at 1:00pm Pacific

Announcements
- Braid Collaboration Sessions @ Internet Archive
  - Tuesday, July 9th: 11:00am–5:00pm
  - Wednesday, July 10th: 11:00am–5:00pm
  - Share the [Invitation](https://docs.google.com/document/d/1SQT-cYDqLAWr--WMGmtAe1iw6-15Hb5BNQFNsponOII/edit?usp=sharing)!
- Mike will present Braid demos @ [dweb lightning talks](https://www.eventbrite.com/e/dweb-sf-meetup-dweb-camp-sneak-peek-in-person-tickets-940716206497?aff=oddtdtcreator)
  - Wednesday at 5:30pm
- New IETF submission: [draft-toomim-httpbis-versions-00](https://datatracker.ietf.org/doc/html/draft-toomim-httpbis-versions-00)

Demos
- Greg: Release of new [dom-diff library](https://www.npmjs.com/package/@braidjs/dom-diff)
  - Mike: Interesting use-case: [improving Youtube Embed](https://frontendmasters.com/blog/youtube-embeds-are-bananas-heavy-and-its-fixable/) performance
- Greg: Braidify your OS with FS ↔ WWW proxy

Discussion
- Mike: New [Versions](https://datatracker.ietf.org/doc/html/draft-toomim-httpbis-versions-00) spec
- Mike: New HTTP Multiresponse idea (below)

<video style='width: calc(100vw - 140px)' controls><source src="https://invisiblecollege.s3.us-west-1.amazonaws.com/braid-meeting-89.mp4#t=1" type="video/mp4"></source></video><br><br>

## Mike: HTTP Multiresponse

I propose `104 Multiresponse` as a better way to push updates. It would work like this:

```
      Request:

         GET /chat
         Version: "3"
         Parents: "1a", "1b"

      Response:

         HTTP/1.1 104 Multiresponse
         Current-Version: "3"

         HTTP/1.1 200 OK
         Version: "2"
         Parents: "1a", "1b"
         Content-Type: application/json
         Content-Length: 64

         [{"text": "Hi, everyone!",
           "author": {"link": "/user/tommy"}}]

         HTTP/1.1 200 OK
         Version: "3"
         Parents: "2"
         Content-Type: application/json
         Content-Length: 117

         [{"text": "Hi, everyone!",
           "author": {"link": "/user/tommy"}}
          {"text": "Yo!",
           "author": {"link": "/user/yobot"}]

```

This "Multiresponse" idea feels very smooth and general. You could use it for a lot of things in HTTP.

Our current subscriptions [can't toggle](https://github.com/braid-org/braid-spec/issues/110) the state of a resource between being deleted `404` and OK `200`, but a Multiresponse can.