Per Connection Buffering

[amydevs]

Specification

A per connection buffer should be created in order to govern the total throughput of the entire connection. This will allow us to put a maximum cap on data being sent per connection on the buffer.

Spec TBD...

Additional context

Tasks

1. Spec this out
2. ...
3. ...

[CMCDragonkai]

Also no stream limit per connection yet! That should also exist.

[CMCDragonkai]

Do note that the underlying ws transport may one day expose websockets themselves as the streams, and whatever is the underlying transport for that can be used as the connection.

But currently this relies HTTP1.1+TCP+WS as the connection, and we built streams on top.

As mentioned before technically HTTP2 supports HTTP2+TCP as the connection with WS as streams, but no support for this atm.

Most likely HTTP3 comes along, and WS becomes built on top of web transport.