[ 
https://issues.apache.org/jira/browse/HTTPCLIENT-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16612342#comment-16612342
 ] 

Oleg Kalnichevski commented on HTTPCLIENT-1942:
-----------------------------------------------

{quote}Does that mean that multiplexing and ALPN negotiation are currently 
mutually exclusive?
{quote}
Only if one does not want to be bothered with manual connection management, in 
which case HttpClient leases one connection per message exchange at present. 
All pushed responses get multiplexed though.
{quote}I'm not sure I follow, since the reactive streaming is protocol-agnostic.
{quote}
All right. If you could put together some Reactive Streams based examples to be 
shipped with the release distribution it would help a great deal with 
understanding of how you envisage the usage of the new APIs. I imagine that 
ultimately the users would want something that hides HttpCore low level 
machinery behind a facade along the lines of 

{code}
public class ReactiveRequestExecutor {

    public Future<Message<HttpResponse, Publisher<ByteBuffer>>> execute(
            HttpRequest request,
            EntityDetails entityDetails,
            Publisher<ByteBuffer> publisher) {
...
    }
}
{code}

Oleg


> Add support for Reactive Streams
> --------------------------------
>
>                 Key: HTTPCLIENT-1942
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1942
>             Project: HttpComponents HttpClient
>          Issue Type: Wish
>          Components: HttpClient (async)
>    Affects Versions: 5.0 Beta1
>            Reporter: Ryan Schmitt
>            Priority: Major
>              Labels: stuck, volunteers-wanted
>             Fix For: Future
>
>         Attachments: client to server tput.jpeg, client to server window 
> scaling (bytes out).jpeg, server to client tput.jpeg
>
>
> It would be very helpful to me if the Apache client provided an 
> implementation of the [Reactive Streams|http://www.reactive-streams.org/] 
> spec, particularly as an implementation of the standard 
> [interfaces|https://search.maven.org/artifact/org.reactivestreams/reactive-streams/1.0.2/jar].
>  These interfaces are JDK6-compatible and have no other dependencies, but 
> they unlock interoperability with many other frameworks, such as RxJava.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org

Reply via email to