Open mikegwhit opened 5 months ago
CC @QuantGeekDev
I pulled in changes from #3390 today and you have to run his test suite via HTTP2_TEST npm test
which fails. it might be useful if we start with the other separate modules that are mentioned above. i didn't see pillarjs in the list also but assume it is relevant.
CC @QuantGeekDev
I pulled in changes from #3390 today and you have to run his test suite via
HTTP2_TEST npm test
which fails. it might be useful if we start with the other separate modules that are mentioned above. i didn't see pillarjs in the list also but assume it is relevant.
Noted. Going to browse through this
I would love to see this feature come to fruition. Can we maybe rank-order all the tasks we know of from, say, lowest-hanging fruit to highest so that different people can jump into smaller tasks to learn the codebase more effectively? I believe this would be a big win, itself, so that entire subfeatures can get completed before breaking larger tasks down into subtasks. Someone with more knowledge of the existing ExpressJS codebase needs to provide their expertise here, if possible. Otherwise, the rest of the comminity & users should have a good stab at the rank-ordered list.
Hey, this is a great job combining a bunch of the historical context around HTTP2 and Express. Thanks for putting that together. Just wanted to drop a note that we are in the process of building a plan for the project's next few years and if you are interested in being involved in pushing http2 support forward please stick around. We will need help with this but we need to get v5 out the door before we can start it. So you might not get a lot of engagement from collaborators just yet, but please don't take that as ignoring this, just an ordering and prioritization thing.
understandable @wesleytodd i would have assumed as much.. FWIW we discussed yesterday (people in this issue ticket) "why http2":
in general this is the summary:
the net is that while HTTP2 itself might not be so important since there are workarounds with a Nginx gateway pointed at non-SSL HTTP (see important assumption above) and CDN's, there are interesting gains made by rearchitecting Express to handle requests via worker thread pools which could be done alongside HTTP2 work..
working to gather all related info in this ticket, and will track an effort to bring http/2 into either PillarJS (for routing compatibility only) or Express 5.x.
@dougwilson notes here (in 2015!) https://github.com/expressjs/express/issues/2761#issuecomment-142612001 that PillarJS can be used alongside native module.. so we need to assess if this is going to be something that uses express.js or just PillarJS with HTTP/2
https://github.com/expressjs/express/pull/3730 -- most recent work that picks up on #3390
https://github.com/expressjs/express/issues/2781 notes request for push-promises
https://github.com/expressjs/express/pull/3778#issuecomment-479955675 mentions HTTP2
https://github.com/expressjs/express/pull/2237 mentions HTTP/2 support in 2015 for Express5.x
https://github.com/expressjs/express/pull/3390 is a proposal PR for HTTP/2 via https://github.com/expressjs/express/issues/3388
https://github.com/expressjs/express/pull/3390#issuecomment-408646774 is probably the most comprehensive TODO List i have seen
notably he modifies also: superagent supertest cookies cookie-session vhost
also since the start of these efforts we now have chatgpt to help us. after some trial and error i got ChatGPT to provide us a useful TODO list: