[
https://issues.apache.org/jira/browse/IGNITE-13037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17206504#comment-17206504
]
Marty Jones commented on IGNITE-13037:
--------------------------------------
That is excellent news for the thin client!
I would rather not use the thick client since it requires a JVM to be installed
on our production servers and would rather not have that overhead.
I am available to beta test the .net think client for near caches once it is
available if needed.
> .NET: Thin Client Near Cache
> ----------------------------
>
> Key: IGNITE-13037
> URL: https://issues.apache.org/jira/browse/IGNITE-13037
> Project: Ignite
> Issue Type: New Feature
> Components: platforms, thin client
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: .NET
>
> Add near caching for thin clients:
> * Clients can subscribe to change notifications for specific keys
> * Clients use partition awareness to route subscriptions to primary nodes
> * Use existing Thick .NET Client near caching mechanism to handle updates on
> the server side
> * Eviction policy is to be handled by the client code (because multiple
> servers are involved)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
