[
https://issues.apache.org/jira/browse/IGNITE-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173886#comment-15173886
]
Pavel Tupitsyn commented on IGNITE-1419:
----------------------------------------
Vladimir, this approach is fine for classes that just hold a bunch of
properties.
In this case, making writeable property results in a class with inconsistent
behavior. This is just bad design.
Yes, in our current system it is very unlikely for the user to change that
property after starting Ignite, but if you look at this class separately, it is
broken.
And there is no reason to do this.
> .Net: Add optional "raw" flag to binary type configuration.
> -----------------------------------------------------------
>
> Key: IGNITE-1419
> URL: https://issues.apache.org/jira/browse/IGNITE-1419
> Project: Ignite
> Issue Type: Task
> Components: platforms
> Affects Versions: 1.1.4
> Reporter: Vladimir Ozerov
> Assignee: Pavel Tupitsyn
> Fix For: 1.6
>
>
> By default we write .Net objects with field names included. But in some cases
> it is not needed. E.g. when objects are not going to be used in queries.
> Removing field names will speed up serialization/deserialization. We can add
> optional "raw" flag to portable type descriptor to control this behavior.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
