ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Valentin Kulichenko <valentin.kuliche...@gmail.com>
Subject Re: Inconsistent implementation of message and event listening.
Date Thu, 07 May 2015 19:42:36 GMT
Hmm. How they can be different if they use the same mechanisms of
continuous processor, simply delegating to it? :)

Anyway, my opinion is the same - several subscriptions should mean several
notifications.

--
Val

On Thu, May 7, 2015 at 6:53 AM, Pavel Tupitsyn <ptupitsyn@gridgain.com>
wrote:

> I also think that messaging is correct and events is not.
> If you subscribe n times, you should unsubscribe n times.
>
> On Thu, May 7, 2015 at 4:12 PM, Dmitriy Setrakyan <dsetrakyan@apache.org>
> wrote:
>
> > On Thu, May 7, 2015 at 4:18 AM, Vladimir Ozerov <vozerov@gridgain.com>
> > wrote:
> >
> > > Hi,
> > >
> > > If the same message listener is registered twice for the same topic, it
> > > will be notified twice when message arrives.
> > >
> > > For events things are different. If user register listener twice, it
> will
> > > be invoked only once when event occurrs.
> > >
> > > Looks inconsistent and counterintuitive. Looks like we have to handle
> > both
> > > scenarios in the same way. But which way is correct? Thoughts?
> > >
> >
> > The messaging way sounds more logical to me.
> >
> >
> > >
> > > Vladimir.
> > >
> >
>
>
>
> --
> --
> Pavel Tupitsyn
> GridGain Systems, Inc.
> www.gridgain.com
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message