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

Pavel Tupitsyn edited comment on IGNITE-2703 at 7/20/16 3:21 PM:
-----------------------------------------------------------------

1) Done
2) .NET and Java store different type names for the same type id. We have to 
use some kind of a composite key for .NET. However, this well break 
compatibility with older versions which expect int keys.

We can keep the extra cache, and use composite keys in there. So that if 
similar need emerges in other platforms, that cache is reused.

In 2.0 we'll move to a single cache with composite keys.


was (Author: ptupitsyn):
1) Done
2) .NET and Java store different type names for the same type id. We have to 
use some kind of a composite key for .NET.

> .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.7
>
>
> 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)

Reply via email to