Ben Christensen
Ben Christensen
Let's rewrite the Rx Design Guidelines as part of the reactivex.io site.
RxApacheHttp has been extracted from RxJava prior to 1.0 as per https://github.com/ReactiveX/RxJava/issues/589 I have done this with a simply copy/paste/commit for now. Commit history remains in the 0.20.x branch of...
@daveray There are a few breaking changes that need fixing before RxClojure can be released. Can you help out? They should be minor.
RxGroovy has been extracted from RxJava prior to 1.0 as per https://github.com/ReactiveX/RxJava/issues/589 I have done this with a simply copy/paste/commit for now. Commit history remains in the 0.20.x branch of...
We need some examples for the README to demonstrate usage. Perhaps we can add unit test examples with dependencies on other libraries to demonstrate interop?
There are a handful of things in the protocol that benefit from seeing code, or at least pseudo code, to communicate the intent, and guide implementation. For example: - DuplexConnection...
There are currently no known changes to make to the protocol that are needed for us to hit 1.0. Can everyone please take the time to do a top-to-bottom review...
I've received feedback that it would be easier to read the spec if the "Stream Sequences and Lifetimes" content was included inline when the frames are presented. The obvious problem...
ReactiveSocket already support 2 types of flow control mechanisms: - REQUEST_N for application level management of number of items being sent on a stream - LEASE for a Responder to...
Ondrej and I capturing things we're finding to do - [x] requestResponse with Single type - [x] fireAndForget with Single type - [x] adopt yarpl::flowable::Subscriber/Subscription types in core code -...