Re: [quicwg/base-drafts] [feature] Push messaging from server to client (#2664)

[Patrick <[e-mail]>]

well there are a couple of solutions possible. As described in the spec I reference to, WebSockets are used, replicating some of the HTTP headers and a topic. 

With this proposal, I want to reduce friction. Why setup two sockets, if you can handle it via one?

The socket you use for HTTP GET, PUT, POST etc. would have to kept open but could then be used to push information in the other direction.

Think of a multi-repsonse GET request. Super convenient to work with from developers point of view on both ends of the connection. No extra protocol needed, no extra syntax to learn. Just multiple responses to the same GET request, either on an `on change` or a periodic basis, limited to a certain rate by either the client or the server.

**Use-case 1 - chat messages**
```
SUB /messages/
```

initial response
```
290 OK
```

1st data response
```
200 OK
[
  "foo",
  "bar"
]
```

2nd data response (100ms later)
```
200 OK
[
  "foo",
  "bar",
  "boo"
]
```

etc.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/2664#issuecomment-488354470