Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Per Connection Buffering #7

Open
amydevs opened this issue Sep 11, 2023 · 2 comments
Open

Per Connection Buffering #7

amydevs opened this issue Sep 11, 2023 · 2 comments
Labels
development Standard development r&d:polykey:core activity 4 End to End Networking behind Consumer NAT Devices

Comments

@amydevs
Copy link
Contributor

amydevs commented Sep 11, 2023

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. ...
@amydevs amydevs added the development Standard development label Sep 11, 2023
@CMCDragonkai
Copy link
Member

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

@CMCDragonkai
Copy link
Member

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.

@CMCDragonkai CMCDragonkai added the r&d:polykey:core activity 4 End to End Networking behind Consumer NAT Devices label Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
development Standard development r&d:polykey:core activity 4 End to End Networking behind Consumer NAT Devices
Milestone
No milestone
Development

No branches or pull requests
2 participants
@CMCDragonkai @amydevs