-
-
Notifications
You must be signed in to change notification settings - Fork 297
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
State of HTTP/2 push #291
Comments
Push isn’t a priority for me personally. I don’t have any plans to work on it. I would be happy to help guide anyone who wants to try to do the work. Push is mostly wired through internally. It would mostly be a question of finishing the work, adding the public api, and write docs. |
How big of an issue do you think this will be? I've written some Rust already, but I've never actively worked on a bigger codebase. Also I'm not familiar with the h2 push spec, but I might be interested in implementing it. |
I am not sure tbh. I think some of the inner work is done, but I don't recall how much off the top of my head. It would probably be more than a trivial change. |
I can try to write up what is left next time I dive into the code base. |
Why is this issue closed? Support for PUSH seems very experimental so far... |
What's the status on this? It can't be done? I'd like to know if there's a plan for this to be implemented properly, @seanmonstar |
@Karrq the status is the same. The features worked on in this library depend on the priorities of the contributors offering their work. Would you be able to dedicate time to improving the situation here? From reading the linked issues, there doesn't seem like too much more is needed. |
Unfortunately I need the functionality but I don't know how to implement it, otherwise I would have already. |
What is the state of HTTP/2 server push in h2? I couldn't find anything about it in the documentation. Are there any plans to implement it in the future?
The text was updated successfully, but these errors were encountered: