ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-2703) .NET: Dynamically registered classes must use binary serialization if possible
Date Fri, 10 Feb 2017 11:58:41 GMT

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

ASF GitHub Bot commented on IGNITE-2703:
----------------------------------------

GitHub user ptupitsyn opened a pull request:

    https://github.com/apache/ignite/pull/1518

    IGNITE-2703 .NET: Dynamic type registration

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-2703

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/1518.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1518
    
----
commit 792506a63572b0b50e47b11c3a6e54065768ac98
Author: Pavel Tupitsyn <ptupitsyn@apache.org>
Date:   2017-02-10T11:56:55Z

    IGNITE-2703 .NET: Dynamic type registration

----


> .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
>              Labels: .net, breaking-api
>             Fix For: 2.0
>
>
> 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.15#6346)

Mime
View raw message