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.

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

Request Prioritization #54

Closed
reem opened this issue Sep 23, 2014 · 3 comments
Closed

Request Prioritization #54

reem opened this issue Sep 23, 2014 · 3 comments
Labels
A-client Area: client.

Comments

@reem
Copy link
Contributor

reem commented Sep 23, 2014

Should allow for throttling and re-prioritizing requests after they are made.

Servo notes say to talk to Patrick McManus about his work on Necko.

@reem reem added A-client Area: client. servo labels Sep 23, 2014
@reem reem added this to the servo milestone Sep 23, 2014
@seanmonstar
Copy link
Member

Considering that reads and writes for Requests require the programmer to explicitly write(msg) or read(buf), what is the actionable item here?

@reem
Copy link
Contributor Author

reem commented Sep 24, 2014

I think they want the ability to prioritize new TCP connections over old ones by some form of throttling.

@seanmonstar
Copy link
Member

After an irc chat with @mcmanus, it seems the things that can be reasonably done:

  1. For Http 1.x, prioritization has to be done in the client layer. If a new request comes up with a higher priority, some Rust code that's writing to other sockets need to be able to write(msg) less.
  2. Http 2 introduces priorities as part of the protocol, such that the server will handle and respond to requests with a higher priority first.

@seanmonstar seanmonstar removed this from the servo milestone Apr 2, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-client Area: client.
Projects
None yet
Development

No branches or pull requests

2 participants