You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (JIRA)" <ji...@apache.org> on 2017/08/30 17:36:01 UTC
[jira] [Commented] (IGNITE-5924) .NET: Decouple Marshaller from
Ignite
[ https://issues.apache.org/jira/browse/IGNITE-5924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16147656#comment-16147656 ]
Pavel Tupitsyn commented on IGNITE-5924:
----------------------------------------
May be we should introduce {{IIgniteInternal}} interface instead to decouple from concrete implementation.
> .NET: Decouple Marshaller from Ignite
> -------------------------------------
>
> Key: IGNITE-5924
> URL: https://issues.apache.org/jira/browse/IGNITE-5924
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.3
>
>
> {{Marshaller}} class has {{Ignite}} property, which is used everywhere as a convenient accessor.
> With thin client we don't have an {{Ignite}} instance ({{IgniteClient}} is there instead).
> Also, {{Marshaller}} itself only needs {{Ignite.BinaryProcessor}}, which is also tied to JNI.
> So the plan is:
> * Add {{IBinaryProcessor}} interface
> * Replace {{Marshaller.Ignite}} with {{Marshaller.BinaryProcessor}}
> * Fix external {{Marshaller.Ignite}} usages in some way
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)