Consider upstreaming support for HTTP/2

[sethmlarson]

Hello!

It's great to see excitement around HTTP/2 and HTTP/3 with urllib3. We've actually unblocked working on HTTP/2 upstream now by adding a Quart and Hypercorn test server and enabling us to start working on HTTP/2 support in earnest. Previously we were hung up on being able to migrate our test suite to be able to use both HTTP/1.1, HTTP/2 and more since there's a lot of value in our test suite. We're tracking that work in this GitHub issue and sub-issues.

I haven't given this a read completely yet, but if I had to guess it's likely based on the work done in this PR by @Ousret. My main question is whether you'd consider collaborating with our team so that more users are able to take advantage of these improvements being made. If not that is okay, but want to be explicit that upstream is open to accepting PRs for HTTP/2 support at this time (and more able to now compared to when that original PR was made).

[Ousret]

Thanks for stopping by!

I did not catch up to the latest advancements. Good advancement for urllib3!
Unfortunately,

First of all, my work didn't get any attractions within a reasonable period of time, six months.
And my vision hasn't changed and it is in direct opposition to urllib3's plans. I cannot maintain both this piece of work and propose an integration that does not suit at all my proposals/architectural ideas.

Right now, it is a modest piece of work, for sure, all things start this way.
This OSS has proven to be very useful, starting with me.

Regards,

[sethmlarson]

Thanks for the reply. If you plan to advertise this project beyond your own use we would appreciate not using the "urllib3.future" name and our logo so as not to cause confusion about association with the urllib3 project.