[
https://issues.apache.org/jira/browse/HTTPCLIENT-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599237#comment-16599237
]
Ryan Schmitt commented on HTTPCLIENT-1942:
------------------------------------------
[~olegk] Interesting. Tell me more; what is the requester responsible for, and
how would we optimize its behavior for reactive streams?
Also, I had one unrelated question: why is Apache 5 targeting Java 7? I can see
two important benefits to targeting Java 8 instead:
1. Interoperability with {{CompletableFuture}} (this may be doable as a
separate JDK8-specific module, to some extent)
2. Default interface methods, which are a game-changer for library maintainers
Of course, this is irrelevant if you have a requirement to support HTTP/2 on
some legacy system.
> 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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
