[
https://issues.apache.org/jira/browse/IGNITE-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16224961#comment-16224961
]
Pavel Tupitsyn commented on IGNITE-6336:
----------------------------------------
[~vozerov]
1) Currently we have three messages with CacheConfiguration:
{{CreateRequest}}}, {{GetOrCreateRequest}}, {{GetConfigurationResponse}}. Each
of them consists solely of CacheConfiguration, so each of these messages can be
extended in future with additional data without compatibility issues. I don't
expect any other message type to carry the CacheConfiguration. Therefore, I see
no reason to include additional length bytes there.
2) Agreed. Added {{CacheClientConfiguration}} class with a possibility to
convert to and from {{CacheConfiguration}}.
3) This is a useful method IMO (and a simple one). For example, if I want to
write an Ignite monitoring utility which shows all the caches with metrics, or
if I want to know whether the cache exists.
> .NET: Thin client: Create cache
> -------------------------------
>
> Key: IGNITE-6336
> URL: https://issues.apache.org/jira/browse/IGNITE-6336
> Project: Ignite
> Issue Type: Improvement
> Components: platforms, thin client
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.4
>
>
> Create, destroy and observer caches from thin client (by name and from
> {{CacheConfiguration}}).
> * {{IIgniteClient.CreateCache}}, {{GetOrCreateCache}} overloads
> * {{ICacheClient.GetConfiguration}}
> * {{IIgnite.GetCacheNames}}
> * {{IIgniteClient.DestroyCache}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
