Skip to content
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

HTTP 2.0 Support #8

Open
saviorand opened this issue Jan 4, 2024 · 3 comments
Open

HTTP 2.0 Support #8

saviorand opened this issue Jan 4, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@saviorand
Copy link
Collaborator

The framework should support sending and receiving HTTP 2.0 requests

@saviorand saviorand changed the title [EPIC] HTTP 2.0 Support HTTP 2.0 Support Apr 14, 2024
@saviorand saviorand added the good first issue Good for newcomers label Apr 14, 2024
@saviorand saviorand added enhancement New feature or request and removed good first issue Good for newcomers labels May 28, 2024
@saviorand saviorand moved this to Backlog in Lightbug's Roadmap May 28, 2024
@mikeball
Copy link

mikeball commented Jun 3, 2024

Could you just skip HTTP/2, and only build out support for HTTP/1.1 and HTTP/3? Seems like that might be better use of limited time given it's significantly different and more performant and the future default choice and build the code base to handle HTTP/3 going forward. I suspect for some time any mojo web apps will be fronted by nginx/caddy and so HTTP/1.1 and plain HTTP should suffice until it needs to run publicly.

@saviorand
Copy link
Collaborator Author

@mikeball Hmm, good point. I think I'll keep this issue open still, but will open a new one for HTTP/3. We'll likely need /2 support in the future at some point still. Thanks for the suggestion!

@saviorand
Copy link
Collaborator Author

Added an issue for HTTP/3 here #53

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants