Re: [infinispan-dev] Reactive Streams + RxJava

On Tue, Jun 20, 2017 at 3:59 AM Galder Zamarreño wrote: > > -- > Galder Zamarreño > Infinispan, Red Hat > > > On 19 Jun 2017, at 15:25, William Burns wrote: > > > > > > > > On Mon, Jun 19, 2017 at 8:34 AM Emmanuel Bernard >

Re: [infinispan-dev] Reactive Streams + RxJava

-- Galder Zamarreño Infinispan, Red Hat > On 19 Jun 2017, at 15:25, William Burns wrote: > > > > On Mon, Jun 19, 2017 at 8:34 AM Emmanuel Bernard > wrote: > You’re thinking about a pure implementation play, correct? RxJava or the > Reactive

Re: [infinispan-dev] Reactive Streams + RxJava

-- Galder Zamarreño Infinispan, Red Hat > On 15 Jun 2017, at 23:20, William Burns wrote: > > I was thinking more about [1] and I find that I was going to implement > basically reactive streams. What we have now in github is similar but it uses > a very crude method of

Re: [infinispan-dev] Reactive Streams + RxJava

On Mon, Jun 19, 2017 at 8:34 AM Emmanuel Bernard wrote: > You’re thinking about a pure implementation play, correct? RxJava or the > Reactive Stream constructs would not be exposed to the user as API. Am I > correct? > Yes, that is correct. This is only for internal

Re: [infinispan-dev] Reactive Streams + RxJava

You’re thinking about a pure implementation play, correct? RxJava or the Reactive Stream constructs would not be exposed to the user as API. Am I correct? Also for posterity, we had backchannel chats about it and you said you felt vert.x was not necessarily addressing your needs. Could you

[infinispan-dev] Reactive Streams + RxJava

I was thinking more about [1] and I find that I was going to implement basically reactive streams. What we have now in github is similar but it uses a very crude method of blocking the thread to prevent back pressure. This can then cause severe issues as many users have found out when they don't