On Thu, 2015-01-08 at 23:15 -0700, Shawn Heisey wrote:
On 1/8/2015 5:28 PM, Stefan Magnus Landrø wrote:
Maybe consider jetty instead?
https://github.com/eclipse/jetty.project/blob/jetty-http2/jetty-http2/http2-client/src/test/java/org/eclipse/jetty/http2/client/Client.java
For an Apache project like Solr (which uses HttpClient and is my primary
reason for being here), I see two problems with that idea:
One problem is the eating your own dog food argument -- if software
from an Apache project fits all of the requirements and has no
significant disadvantages compared to a competitor, we should choose to
use the software from Apache. Both projects are likely to benefit.
http://en.wikipedia.org/wiki/Eating_your_own_dog_food
The other problem is that switching to a completely different http
client would likely involve significant development time, both for the
switch itself and for fixing the inevitable bugs that are a direct result.
Seeing that competing projects are already focusing effort on HTTP/2 is
even more reason to accelerate HttpClient towards HTTP/2.
Even Oracle has fairly concrete plans for a new client in Java itself:
https://bugs.openjdk.java.net/browse/JDK-8042950
Thanks,
Shawn
Shawn,
I can work on HC in my spare time only. Even if I quit my day job and
divorce my wife I am not sure HTTP/2.0 in HC by the end of February is
realistic. The best case scenario would be having BETA quality support
for HTTP/2.0 by the end of year.
Oleg
-
To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org
For additional commands, e-mail: httpclient-users-h...@hc.apache.org