[
https://issues.apache.org/jira/browse/SOLR-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516880#comment-14516880
]
Shalin Shekhar Mangar commented on SOLR-7442:
---------------------------------------------
You misunderstand Karl. HTTP/2 is not a back-compat break. Clients which
support HTTP/2 can negotiate an ugprade whereas old HTTP/1.1 clients will just
continue to work as-is. So I see no reason why a new httpclient such as Jetty's
http client will not work with old Solr installations. Similiarily an old Solrj
can continue to work with Solr which has http/2 enabled. Of course, we will
test such combinations before we release.
> 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]
