[
https://issues.apache.org/jira/browse/SOLR-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101965#comment-15101965
]
Shawn Heisey commented on SOLR-7442:
------------------------------------
While looking into SOLR-8539, I remembered this issue. Netty also supports
HTTP/2, so that's another possible option for a replacement.
How much pain would it cause to have support for both HttpClient and another
library in SolrJ 6.x? We could add a second library for HTTP/2 without
dropping support for existing code. Once HttpClient finally gets HTTP/2
support, we can evaluate which client we want to stick with on a long term
basis, deprecate the other, and remove it in 7.0.
Based on my reading of the HTTP/2 spec, I believe it will allow for some
performance improvement for Solr and SolrJ. It probably will not be a
significant improvement on a LAN, but there are service providers that set up
Solr for customers that access it over the Internet, where HTTP/2 really shines.
> HttpClient replacement for HTTP/2.0
> -----------------------------------
>
> Key: SOLR-7442
> URL: https://issues.apache.org/jira/browse/SOLR-7442
> Project: Solr
> Issue Type: New Feature
> Reporter: Ishan Chattopadhyaya
>
> Given that it would take about a year for Apache HC's HttpClient to support
> HTTP/2 (as per [~olegk] in SOLR-6865), adding this issue for exploring the
> way forward. It would be preferable to move to HTTP/2 and be able to use
> features like async http calls. Maybe we could look for alternatives to HC
> HttpClient, (e.g. Jetty's HttpClient)?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
