[
https://issues.apache.org/jira/browse/SOLR-12297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16459859#comment-16459859
]
Mark Miller commented on SOLR-12297:
------------------------------------
It's very easy to add an HTTP2 connector to Jetty, just swap in the right
config, it's a lot more work to have HTTP2 user clients and internal clients
that can actually do anything with it. Our clients don't support talking to
HTTP2 so I'm not sure how that would actually work unless it was single server
Solr with no internal communication. The clients also need new async API
options. This is about that work.
One option is Apache HttpClient 5 I guess, but I've been playing around with
Jetty HttpClient instead, given there past interest and effort with helping the
project and the fact that we use Jetty for the container.
> Create a good SolrClient for SolrCloud.
> ---------------------------------------
>
> Key: SOLR-12297
> URL: https://issues.apache.org/jira/browse/SOLR-12297
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Mark Miller
> Priority: Major
>
> Blocking or async support as well as HTTP2 compatible with multiplexing.
> Once it supports enough and is stable, replace internal usage, allowing
> async, and eventually move to HTTP2 connector and allow multiplexing. Could
> support HTTP1.1 and HTTP2 on different ports depending on state of the world
> then.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
