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

Base ideology of connections #7

Open

Vect0rZ opened this issue Sep 19, 2019 · 0 comments

Owner

Vect0rZ commented Sep 19, 2019

What does that mean
Currently the Server acts as a continuously running entity on a single connection, awaiting packets.

What is the expectation
The connection should be handled exactly as HTTP/2's idea of "reusing" connections, rather than a long-running instance.

Example

You open up a website, that needs to load a html page and a css file and a logo. How should QUIC handle this:

Connection has been opened

A bidirectional stream is opened for the HTML
A bidirectional stream is opened for the CSS
A bidirectional stream is opened for the logo

All of those are interleaved in a single connection.
Each of the streams is being closed by RESET_SREAM frames in the last data packets or immediately in a single packet.
After all of the streams are closed, a CONNECTION_CLOSE is being send by the server to disband the client/server connection.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment