Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Mon, 29 Aug 2016 14:17:20 +0000 (UTC)
From: "Pavel Tupitsyn (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.12940775.1455969830000.436375.1472480240546@Atlassian.JIRA>
In-Reply-To: <JIRA.12940775.1455969830000@Atlassian.JIRA>
References: <JIRA.12940775.1455969830000@Atlassian.JIRA> <JIRA.12940775.1455969830292@arcas>
Subject: [jira] [Commented] (IGNITE-2703) .NET: Dynamically registered
 classes must use binary serialization if possible.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 29 Aug 2016 14:17:22 -0000


    [ https://issues.apache.org/jira/browse/IGNITE-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15446002#comment-15446002 ] 

Pavel Tupitsyn commented on IGNITE-2703:
----------------------------------------

Blocked by IGNITE-3796: need to reuse the platforms cache.

> .NET: Dynamically registered classes must use binary serialization if possible.
> -------------------------------------------------------------------------------
>
>                 Key: IGNITE-2703
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2703
>             Project: Ignite
>          Issue Type: Task
>          Components: platforms
>    Affects Versions: 1.5.0.final
>            Reporter: Vladimir Ozerov
>            Assignee: Pavel Tupitsyn
>            Priority: Critical
>              Labels: .net, roadmap
>             Fix For: 1.8
>
>
> At present we support dynamic class registration in .NET, but they are written using deafult .NET mechanism. This is counterintuitive for users and not consistent with Java, where such classes are written in binary form.
> Proposed implementation plan:
> 1) For each dynamically registered class we must understand whether it could be serialized through binary or not. If not - print a warning and fallback to .NET.
> 2) Before writing a class we must ensure that it's [typeId -> name] pair is known to the cluster. If not - write full class name instead of type ID. Java already do that.
> 3) Last, to support backward compatibility we must be able to fallback to current mode with help of some boolean flag.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)