Hi,
First things first, let me clarify that I didn't request the feature myself
so I'm not advocating it ;-)
We have a vague proposition in a JIRA ticket, and my intention is to try
give it some objective essence. The team can happily close the ticket with
a "Won't Fix" if we feel that there's
or Akka (after wrapping/fluent-conversion, of course):
> >
> > getData().to(Streams::from).dispatchOn(...)
> >
> > Although I'm pretty confident that RxJava 2.0 works right now, it is
> still
> > considered alpha and based on past experience with its gatekeepers, it
the
> > following
> > > getData() may return an RxJava Observable and still be consumable via
> > > Reactor or Akka (after wrapping/fluent-conversion, of course):
> > >
> > > getData().to(Streams::from).dispatchOn(...)
> > >
> > > Although I'm pretty confident that RxJava 2.0 works right now, it is
> > still
> > > considered alpha and based on past experience with its gatekeepers, it
> > may
> > > take 6-12 months until an official release comes out.
> > >
> > >
> > >
> > > --
> > > View this message in context:
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Brainstorming-about-Reactive-Streams-tp3346p3422.html
> > > Sent from the Apache Ignite Developers mailing list archive at
> > Nabble.com.
> > >
> >
>
libraries:
> > > >
> > > > Observable.fromPublisher(getData()).map().filter().group()...
> > > >
> > > > I'm not sure about the others, but RxJava 2.0 Observable (which later
> > may
> > > > be
> > > > renamed to Flowabl
; of
> > > > the libraries:
> > > >
> > > > Observable.fromPublisher(getData()).map().filter().group()...
> > > >
> > > > I'm not sure about the others, but RxJava 2.0 Observable (which later
> > may
> > > > be
> > >
llowing API is inconvenient to use but is
> > definitely
> > > > > cutting-edge:
> > > > >
> > > > > Publisher getData();
> > > > >
> > > > > but you can only subscribe to it in its plain form or wrap it with
> > one
&
Yeah, the idea would be to wrap RxJava 1.0 with the adapter and only use
the Reactive Streams API where possible from within Ignite.
Nevertheless, the ReactiveX API would also be accessible in case we want to
do stuff with Hystrix too.
Raúl.
On 20 Sep 2015 16:39, "Vishal Garg"
https://github.com/ReactiveX/RxJava/wiki/R
eactive-Streams
+1 on your approach ( if we are wrapping 1.0 with adapters??)
Raul it looks like there is a path to convergence in RxJava 2.0, but above link
mentions that you could use the standard + integration modules with wrappers on
core 1.0 Apis.
Hey Igniters,
Lalit Kumar Jha expressed interest [1] in contributing to ticket IGNITE-815
[2] which aims to bring in Reactive Streams to Ignite.
I wanted to start a brainstorm about which functionalities we'd like to
cover.
Off the top of my head, I can think of merging, filtering, sorting,
Yes, lets first explore how reactive-streams can be useful for Ignite.
Adding one more candidate to list http://projectreactor.io/docs/, as this
project:
Is for fast-data applications
Team are core contributors to the Reactive Streams Specification
10 matches
Mail list logo
