ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Tupitsyn (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3689) .NET: Remove IgniteProxy
Date Mon, 17 Apr 2017 08:39:41 GMT

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

Pavel Tupitsyn commented on IGNITE-3689:

Injected Ignite instance may be serialized due to {{MessageListenerHolder}} behavior, among
other things.
So we should keep a null-valued field in serialized form.

However, simple system type write handler is a better solution than a proxy class.

> .NET: Remove IgniteProxy
> ------------------------
>                 Key: IGNITE-3689
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3689
>             Project: Ignite
>          Issue Type: Improvement
>          Components: platforms
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>              Labels: .NET, breaking
>             Fix For: 2.0
> IgniteProxy exists to handle serialization of injected IIgnite fields in user classes.
> As a result, we write a type id and a null flag in place of injected fields.
> Instead we should just skip injected fields altogether.
> There are two cases:
> * Binarizable. In this case we can use a special no-op serializer or add a check to BinaryWriter.
> * Serializable. Override ISerializable in Ignite and don't write anything.

This message was sent by Atlassian JIRA

View raw message