[
https://issues.apache.org/jira/browse/IGNITE-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15191061#comment-15191061
]
Pavel Tupitsyn commented on IGNITE-2703:
----------------------------------------
> we must understand whether it could be serialized through binary or not
I can't imagine a case when a class CAN'T be serialized with reflective
serializer, can you give an example?
> to support backward compatibility we must be able to fallback to current
> mode with help of some boolean flag.
Do we need a flag? Can we just write all serializable classes in the old way,
and use dynamic registration for non-serializable classes?
> .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
> Fix For: 1.6
>
>
> 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)
