Hi Dmitriy,
My question regarding cache interceptor availability in .Net is still
outstanding.
I have working code using a continuous query, but am interested in cache
interceptor if this is a better solution.
Thanks.
Raymond.
*From:* Dmitry Pavlov [mailto:
[hidden email]]
*Sent:* Wednesday, May 16, 2018 3:45 AM
*To:*
[hidden email]
*Cc:*
[hidden email]
*Subject:* Re: Using a cache as an affinity co-located processing buffer in
Ignite.Net
Hi Raymond,
Was this question answered?
Sincerely,
Dmitriy Pavlov
вт, 1 мая 2018 г. в 0:20, Raymond Wilson <
[hidden email]>:
Cross posting to dev list for comment on cache interceptor availability on
Ignite .Net client.
-----Original Message-----
From: Raymond Wilson [mailto:
[hidden email]]
Sent: Saturday, April 28, 2018 10:35 PM
To: '
[hidden email]' <
[hidden email]>
Subject: RE: Using a cache as an affinity co-located processing buffer in
Ignite.Net
Further investigation shows CacheInterceptor is not a part of the
Ignite.NET API.
Is there a plan/ticket for this to be done?
-----Original Message-----
From: Raymond Wilson [mailto:
[hidden email]]
Sent: Saturday, April 28, 2018 1:08 PM
To:
[hidden email]
Subject: Re: Using a cache as an affinity co-located processing buffer in
Ignite.Net
Val,
Are the interceptors invoked in the affinity co-located context of the
item? The help is a little unclear on that.
Thanks,
Raymond.
Sent from my iPhone
> On 28/04/2018, at 12:12 PM, vkulichenko <
[hidden email]>
wrote:
>
> Raymond,
>
> If you go with approach I described above, I would actually recommend to
use
> interceptors:
>
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/CacheInterceptor.html
>
> Continuous query seems to be a bit cumbersome for this.
>
> -Val
>
>
>
> --
> Sent from:
http://apache-ignite-users.70518.x6.nabble.com/
Locked
