I personally think that this feature should be implemented in Ignite,
though maybe we should first start from Continuous Queries for thin
clients.
Best Regards,
Igor
On Mon, May 25, 2020 at 6:15 PM Pavel Tupitsyn wrote:
> Marty,
>
> Continuous queries are certainly planned for thin clients,
>
Marty,
Continuous queries are certainly planned for thin clients,
and that is the best way to get cache update notifications.
On Fri, May 22, 2020 at 8:32 PM Marty Jones wrote:
> Has there been a request for event listeners for the thin clients? I am
> happy to roll my own implementation of
Has there been a request for event listeners for the thin clients? I am
happy to roll my own implementation of the nearcache if I can get the
events of when cache items within the cluster are added, modified, or
deleted.
On Thu, May 21, 2020 at 2:29 PM Marty Jones wrote:
> Honestly near cache
Honestly near cache for the thin client is a must for me. Implementing
this is a huge performance gain.
On Thu, May 21, 2020 at 5:47 AM Pavel Tupitsyn wrote:
> Alex,
>
> I've recently implemented .NET Native Near Cache [1].
> It is a very similar concept, because caching is performed on
Alex,
I've recently implemented .NET Native Near Cache [1].
It is a very similar concept, because caching is performed on platform side.
We had requests for this from different users for quite some time.
Users were implementing this on their own with Continuous Queries.
Yes, it is not
Hello,
I don't think that near cache for thin client on Ignite level it's a
good idea.
Expiration is not the only case here. For thick clients near caches are
transactionally consistent. For thin clients such a guarantee never can be
provided.
Near cache for thin clients will be either too heavy
Ok, thanks for the explanation.
Yes, this is a good feature, and I've had this in mind for some time.
Ticket filed: https://issues.apache.org/jira/browse/IGNITE-13037
There are no immediate plans, but I think there is a possibility to achieve
this by the end of the year.
On Tue, May 19, 2020 at
The use case is having a local cache that stores most widely used cache
items in memory on server instead of having the network expense of pulling
them down every time they are requested. The main thing is the near cache
has to support removing cache items that have expired on the server.
The
Can you please describe the use case in more detail?
What do you expect from such a feature?
On Tue, May 19, 2020 at 2:01 AM martybjo...@gmail.com
wrote:
> I wanted to see if there are any plans to support near caches for thin
> clients? I think it would be a great feature. I know I could use
I wanted to see if there are any plans to support near caches for thin
clients? I think it would be a great feature. I know I could use it right
now.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
10 matches
Mail list logo
