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 2016/04/01 16:27:25 UTC

[jira] [Commented] (IGNITE-1873) .Net: Investigate BinaryFormatter vs DataContractSerializer vs XmlSerializer

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

Pavel Tupitsyn commented on IGNITE-1873:
----------------------------------------

Dynamic registration (IGNITE-2703) makes this obsolete.

> .Net: Investigate BinaryFormatter vs DataContractSerializer vs XmlSerializer
> ----------------------------------------------------------------------------
>
>                 Key: IGNITE-1873
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1873
>             Project: Ignite
>          Issue Type: Improvement
>          Components: platforms
>    Affects Versions: 1.6
>            Reporter: Pavel Tupitsyn
>            Priority: Minor
>
> DataContractSerializer and XmlSerializer, in binary mode (BinaryWriter), are said to be faster and produce more compact results than BinaryFormatter.
> We can consider changing it in SerializableObjectHolder. Need to run benchmarks first.
> Comprehensive feature comparison: http://manski.net/2014/10/net-serializers-comparison-chart/



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