Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
noopside
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
by
noopside
2y ago
neither does this alternative
2.
▲
Show HN: Compete with compiled aiohttp using HTTP/2 and HTTP/3
(github.com)
1 points
by
noopside
2y ago
|
0 comments
3.
▲
Revived the promise made six years ago for Requests 3
(gist.github.com)
7 points
by
noopside
2y ago
|
0 comments
4.
▲
Support Happy Eyeballs Even with QUIC / HTTP3 in Python
(github.com)
1 points
by
noopside
3y ago
|
0 comments
5.
▲
by
noopside
3y ago
will be glad to answer any concerns if you encounter any, the repo issue tracker will welcome your feedbacks.
6.
▲
by
noopside
3y ago
Glad to hear that. This is actually planned, the miscellaneous control for networking fingerprint (mimic chrome tls handshake). will come soon enough. for now, my own experience shows that it is more resilient as is (with appropriate header
7.
▲
by
noopside
3y ago
there https://github.com/jawah/urllib3.future/issues
8.
▲
by
noopside
3y ago
This would be done gladly. Open an issue at urllib3.future and a proper tracking will be made. The internal resolver is recursive, so CNAME are automatically translated into addresses. What remain is the happy eyeball implementation, which
9.
▲
by
noopside
3y ago
Not yet, but is coming soon. We have a minor technical challenge to make it work with QUIC.
10.
▲
Show HN: Niquests – a simple HTTP library, a drop-in replacement for Requests
(github.com)
44 points
by
noopside
3y ago
|
12 comments
11.
▲
Urllib3.future is as BoringSSL is to OpenSSL but to urllib3 with support
(github.com)
1 points
by
noopside
3y ago
|
0 comments
12.
▲
by
noopside
3y ago
Great question, In a nutshell, Niquests goes way beyond httpx capabilities by actually leveraging HTTP/2+ protocols, they are quite shy on its support (HTTP/2) due to the current inability of issuing concurrent requests in a synch
13.
▲
by
noopside
3y ago
Many things, starting with true support for recent protocols. Until now, no solution were able to leverage multiplexing and couldn't issue concurrent requests using one connection. This permit to avoid useless threading and complexity.
14.
▲
The biggest leap forward in HTTP clients for Python in years
(github.com)
23 points
by
noopside
3y ago
|
5 comments