[
https://issues.apache.org/jira/browse/IGNITE-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105455#comment-15105455
]
Pavel Tupitsyn edited comment on IGNITE-2285 at 1/18/16 3:59 PM:
-----------------------------------------------------------------
You may be right about rare usage, but still, user will typically have a cache
instance in hand, so why bother him with cache name and generics again? You can
see how it simplifies the code in the diff.
Also, this method may be easier to discover and understand for a new Ignite
user (through intellisense or object browser).
This change is very trivial, I do not see a single reason to not have it.
was (Author: ptupitsyn):
You may be right about rare usage, but still, user will typically have a cache
instance in hand, so why bother him with cache name and generics again? You can
see how it simplifies the code in the diff.
This change is very trivial, I do not see a single reason to not have it.
> .Net: Add ICache.GetDataStreamer
> --------------------------------
>
> Key: IGNITE-2285
> URL: https://issues.apache.org/jira/browse/IGNITE-2285
> Project: Ignite
> Issue Type: Improvement
> Components: interop
> Affects Versions: 1.1.4
> Reporter: Pavel Tupitsyn
> Assignee: Vladimir Ozerov
> Fix For: 1.6
>
>
> Currently we have IIgnite.GetDataStreamer, where user has to specify cache
> name and generic arguments.
> ICache.GetDataStreamer will infer both cache name and generic types for the
> user.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
