You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Roi Apelker <Ro...@amdocs.com> on 2017/08/07 16:14:07 UTC
continuous query internal mechanism
Hello,
I am trying to look into the code of the continuous query mechanism - where the GEODE server sends the notification back to the client.
Can anyone point me to the central classes of continuous query, especially to the one that is responsible for the calculation of the new data and packing it as a message back to the client?
Thanks,
Roi
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
RE: continuous query internal mechanism
Posted by Roi Apelker <Ro...@amdocs.com>.
Dhanyavad
-----Original Message-----
From: Anilkumar Gingade [mailto:agingade@pivotal.io]
Sent: Tuesday, August 08, 2017 9:55 PM
To: dev@geode.apache.org
Subject: Re: continuous query internal mechanism
Registered events, i meant, are events generated for interest registration "region.registerInterest(*)". And CqEvents are for CQs registered.
-Anil.
On Tue, Aug 8, 2017 at 12:27 AM, Roi Apelker <Ro...@amdocs.com> wrote:
> Shukriya
>
> What is the difference between registered events and CQ events?
>
> -----Original Message-----
> From: Anilkumar Gingade [mailto:agingade@pivotal.io]
> Sent: Monday, August 07, 2017 10:12 PM
> To: dev@geode.apache.org
> Subject: Re: continuous query internal mechanism
>
> CQ Processing on server side is same for all clients (Java, C++)...
>
> The subscription events are sent to client as ClientUpdateMessage,
> which holds information about registered events and CQ events. The
> client process this and updates/invokes the client side
> cache/listeners with respective event. Look into
> ClientUpdateMessageImpl and CacheClientUpdater (for client side processing).
>
> -Anil.
>
>
>
>
> On Mon, Aug 7, 2017 at 11:01 AM, Roi Apelker <Ro...@amdocs.com>
> wrote:
>
> > Thanks,
> >
> > By the way, is there any difference in the behaviour of the server,
> > if the client that registered the CQ is a native (C++) client?
> >
> > I have been going over the classes and code for some time and can't
> > seem to find the actual location where a CQ update/notification is
> sent...
> >
> > It's like CqEventImpl class is never even generated in this scenario.
> >
> > If anyone can help here I would be most grateful :-)
> >
> > Thanks
> >
> > Roi
> >
> >
> >
> > -----Original Message-----
> > From: Anilkumar Gingade [mailto:agingade@pivotal.io]
> > Sent: Monday, August 07, 2017 8:23 PM
> > To: dev@geode.apache.org
> > Subject: Re: continuous query internal mechanism
> >
> > You can find those in CqServiceImpl.process*()...
> >
> > -Anil.
> >
> >
> > On Mon, Aug 7, 2017 at 9:14 AM, Roi Apelker <Ro...@amdocs.com>
> > wrote:
> >
> > > Hello,
> > >
> > > I am trying to look into the code of the continuous query
> > > mechanism
> > > - where the GEODE server sends the notification back to the client.
> > >
> > > Can anyone point me to the central classes of continuous query,
> > > especially to the one that is responsible for the calculation of
> > > the new data and packing it as a message back to the client?
> > >
> > > Thanks,
> > >
> > > Roi
> > >
> > > This message and the information contained herein is proprietary
> > > and confidential and subject to the Amdocs policy statement,
> > >
> > > you may review at https://www.amdocs.com/about/email-disclaimer <
> > > https://www.amdocs.com/about/email-disclaimer>
> > >
> > This message and the information contained herein is proprietary and
> > confidential and subject to the Amdocs policy statement,
> >
> > you may review at https://www.amdocs.com/about/email-disclaimer <
> > https://www.amdocs.com/about/email-disclaimer>
> >
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
>
> you may review at https://www.amdocs.com/about/email-disclaimer <
> https://www.amdocs.com/about/email-disclaimer>
>
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
Re: continuous query internal mechanism
Posted by Anilkumar Gingade <ag...@pivotal.io>.
Registered events, i meant, are events generated for interest registration
"region.registerInterest(*)". And CqEvents are for CQs registered.
-Anil.
On Tue, Aug 8, 2017 at 12:27 AM, Roi Apelker <Ro...@amdocs.com> wrote:
> Shukriya
>
> What is the difference between registered events and CQ events?
>
> -----Original Message-----
> From: Anilkumar Gingade [mailto:agingade@pivotal.io]
> Sent: Monday, August 07, 2017 10:12 PM
> To: dev@geode.apache.org
> Subject: Re: continuous query internal mechanism
>
> CQ Processing on server side is same for all clients (Java, C++)...
>
> The subscription events are sent to client as ClientUpdateMessage, which
> holds information about registered events and CQ events. The client process
> this and updates/invokes the client side cache/listeners with respective
> event. Look into ClientUpdateMessageImpl and CacheClientUpdater (for client
> side processing).
>
> -Anil.
>
>
>
>
> On Mon, Aug 7, 2017 at 11:01 AM, Roi Apelker <Ro...@amdocs.com>
> wrote:
>
> > Thanks,
> >
> > By the way, is there any difference in the behaviour of the server, if
> > the client that registered the CQ is a native (C++) client?
> >
> > I have been going over the classes and code for some time and can't
> > seem to find the actual location where a CQ update/notification is
> sent...
> >
> > It's like CqEventImpl class is never even generated in this scenario.
> >
> > If anyone can help here I would be most grateful :-)
> >
> > Thanks
> >
> > Roi
> >
> >
> >
> > -----Original Message-----
> > From: Anilkumar Gingade [mailto:agingade@pivotal.io]
> > Sent: Monday, August 07, 2017 8:23 PM
> > To: dev@geode.apache.org
> > Subject: Re: continuous query internal mechanism
> >
> > You can find those in CqServiceImpl.process*()...
> >
> > -Anil.
> >
> >
> > On Mon, Aug 7, 2017 at 9:14 AM, Roi Apelker <Ro...@amdocs.com>
> > wrote:
> >
> > > Hello,
> > >
> > > I am trying to look into the code of the continuous query mechanism
> > > - where the GEODE server sends the notification back to the client.
> > >
> > > Can anyone point me to the central classes of continuous query,
> > > especially to the one that is responsible for the calculation of the
> > > new data and packing it as a message back to the client?
> > >
> > > Thanks,
> > >
> > > Roi
> > >
> > > This message and the information contained herein is proprietary and
> > > confidential and subject to the Amdocs policy statement,
> > >
> > > you may review at https://www.amdocs.com/about/email-disclaimer <
> > > https://www.amdocs.com/about/email-disclaimer>
> > >
> > This message and the information contained herein is proprietary and
> > confidential and subject to the Amdocs policy statement,
> >
> > you may review at https://www.amdocs.com/about/email-disclaimer <
> > https://www.amdocs.com/about/email-disclaimer>
> >
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
>
> you may review at https://www.amdocs.com/about/email-disclaimer <
> https://www.amdocs.com/about/email-disclaimer>
>
RE: continuous query internal mechanism
Posted by Roi Apelker <Ro...@amdocs.com>.
Shukriya
What is the difference between registered events and CQ events?
-----Original Message-----
From: Anilkumar Gingade [mailto:agingade@pivotal.io]
Sent: Monday, August 07, 2017 10:12 PM
To: dev@geode.apache.org
Subject: Re: continuous query internal mechanism
CQ Processing on server side is same for all clients (Java, C++)...
The subscription events are sent to client as ClientUpdateMessage, which holds information about registered events and CQ events. The client process this and updates/invokes the client side cache/listeners with respective event. Look into ClientUpdateMessageImpl and CacheClientUpdater (for client side processing).
-Anil.
On Mon, Aug 7, 2017 at 11:01 AM, Roi Apelker <Ro...@amdocs.com> wrote:
> Thanks,
>
> By the way, is there any difference in the behaviour of the server, if
> the client that registered the CQ is a native (C++) client?
>
> I have been going over the classes and code for some time and can't
> seem to find the actual location where a CQ update/notification is sent...
>
> It's like CqEventImpl class is never even generated in this scenario.
>
> If anyone can help here I would be most grateful :-)
>
> Thanks
>
> Roi
>
>
>
> -----Original Message-----
> From: Anilkumar Gingade [mailto:agingade@pivotal.io]
> Sent: Monday, August 07, 2017 8:23 PM
> To: dev@geode.apache.org
> Subject: Re: continuous query internal mechanism
>
> You can find those in CqServiceImpl.process*()...
>
> -Anil.
>
>
> On Mon, Aug 7, 2017 at 9:14 AM, Roi Apelker <Ro...@amdocs.com>
> wrote:
>
> > Hello,
> >
> > I am trying to look into the code of the continuous query mechanism
> > - where the GEODE server sends the notification back to the client.
> >
> > Can anyone point me to the central classes of continuous query,
> > especially to the one that is responsible for the calculation of the
> > new data and packing it as a message back to the client?
> >
> > Thanks,
> >
> > Roi
> >
> > This message and the information contained herein is proprietary and
> > confidential and subject to the Amdocs policy statement,
> >
> > you may review at https://www.amdocs.com/about/email-disclaimer <
> > https://www.amdocs.com/about/email-disclaimer>
> >
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
>
> you may review at https://www.amdocs.com/about/email-disclaimer <
> https://www.amdocs.com/about/email-disclaimer>
>
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
Re: continuous query internal mechanism
Posted by Anilkumar Gingade <ag...@pivotal.io>.
CQ Processing on server side is same for all clients (Java, C++)...
The subscription events are sent to client as ClientUpdateMessage, which
holds information about registered events and CQ events. The client process
this and updates/invokes the client side cache/listeners with respective
event. Look into ClientUpdateMessageImpl and CacheClientUpdater (for client
side processing).
-Anil.
On Mon, Aug 7, 2017 at 11:01 AM, Roi Apelker <Ro...@amdocs.com> wrote:
> Thanks,
>
> By the way, is there any difference in the behaviour of the server, if the
> client that registered the CQ is a native (C++) client?
>
> I have been going over the classes and code for some time and can't seem
> to find the actual location where a CQ update/notification is sent...
>
> It's like CqEventImpl class is never even generated in this scenario.
>
> If anyone can help here I would be most grateful :-)
>
> Thanks
>
> Roi
>
>
>
> -----Original Message-----
> From: Anilkumar Gingade [mailto:agingade@pivotal.io]
> Sent: Monday, August 07, 2017 8:23 PM
> To: dev@geode.apache.org
> Subject: Re: continuous query internal mechanism
>
> You can find those in CqServiceImpl.process*()...
>
> -Anil.
>
>
> On Mon, Aug 7, 2017 at 9:14 AM, Roi Apelker <Ro...@amdocs.com>
> wrote:
>
> > Hello,
> >
> > I am trying to look into the code of the continuous query mechanism -
> > where the GEODE server sends the notification back to the client.
> >
> > Can anyone point me to the central classes of continuous query,
> > especially to the one that is responsible for the calculation of the
> > new data and packing it as a message back to the client?
> >
> > Thanks,
> >
> > Roi
> >
> > This message and the information contained herein is proprietary and
> > confidential and subject to the Amdocs policy statement,
> >
> > you may review at https://www.amdocs.com/about/email-disclaimer <
> > https://www.amdocs.com/about/email-disclaimer>
> >
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
>
> you may review at https://www.amdocs.com/about/email-disclaimer <
> https://www.amdocs.com/about/email-disclaimer>
>
RE: continuous query internal mechanism
Posted by Roi Apelker <Ro...@amdocs.com>.
Thanks,
By the way, is there any difference in the behaviour of the server, if the client that registered the CQ is a native (C++) client?
I have been going over the classes and code for some time and can't seem to find the actual location where a CQ update/notification is sent...
It's like CqEventImpl class is never even generated in this scenario.
If anyone can help here I would be most grateful :-)
Thanks
Roi
-----Original Message-----
From: Anilkumar Gingade [mailto:agingade@pivotal.io]
Sent: Monday, August 07, 2017 8:23 PM
To: dev@geode.apache.org
Subject: Re: continuous query internal mechanism
You can find those in CqServiceImpl.process*()...
-Anil.
On Mon, Aug 7, 2017 at 9:14 AM, Roi Apelker <Ro...@amdocs.com> wrote:
> Hello,
>
> I am trying to look into the code of the continuous query mechanism -
> where the GEODE server sends the notification back to the client.
>
> Can anyone point me to the central classes of continuous query,
> especially to the one that is responsible for the calculation of the
> new data and packing it as a message back to the client?
>
> Thanks,
>
> Roi
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
>
> you may review at https://www.amdocs.com/about/email-disclaimer <
> https://www.amdocs.com/about/email-disclaimer>
>
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
Re: continuous query internal mechanism
Posted by Anilkumar Gingade <ag...@pivotal.io>.
You can find those in CqServiceImpl.process*()...
-Anil.
On Mon, Aug 7, 2017 at 9:14 AM, Roi Apelker <Ro...@amdocs.com> wrote:
> Hello,
>
> I am trying to look into the code of the continuous query mechanism -
> where the GEODE server sends the notification back to the client.
>
> Can anyone point me to the central classes of continuous query, especially
> to the one that is responsible for the calculation of the new data and
> packing it as a message back to the client?
>
> Thanks,
>
> Roi
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
>
> you may review at https://www.amdocs.com/about/email-disclaimer <
> https://www.amdocs.com/about/email-disclaimer>
>