13
0
geforkt von Mirrors/Velocity
Velocity/proxy
Andrew Steinborn d1736bf94c Move from custom HTTP client to Async HTTP Client
The most significant advantage is that Velocity gets a well-tested
HTTP client implementation which also includes a connection pool,
allowing us to avoid the overhead of TCP and TLS handshakes upon each
login.

Unfortunately, Async HTTP Client does not work with the kqueue transport.
Since almost nobody runs a production Velocity server on macOS, we have
decided to remove kqueue support. The benefits that Async HTTP Client
provides outweigh the disadvantages of not having a macOS native transport.
macOS is adequately supported by the normal NIO transport.
2019-07-26 01:29:51 -04:00
..
src Move from custom HTTP client to Async HTTP Client 2019-07-26 01:29:51 -04:00
build.gradle Move from custom HTTP client to Async HTTP Client 2019-07-26 01:29:51 -04:00