You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/10/01 13:52:26 UTC

[jira] [Commented] (IGNITE-1572) .Net: Check if we can get rid of "WritePortableOrSerializable" method.

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

ASF GitHub Bot commented on IGNITE-1572:
----------------------------------------

GitHub user ptupitsyn opened a pull request:

    https://github.com/apache/ignite/pull/122

    IGNITE-1572 .Net: Check if we can get rid of "WritePortableOrSerializable" method.

    Replace WritePortableOrSerializable with WriteObject

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ptupitsyn/ignite ignite-1572

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/122.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #122
    
----
commit f984341062477a8fef7823205d68947b344836ce
Author: ptupitsyn <pt...@gridgain.com>
Date:   2015-10-01T11:51:20Z

    IGNITE-1572 .Net: Check if we can get rid of "WritePortableOrSerializable" method.
    
    Replace WritePortableOrSerializable with WriteObject

----


> .Net: Check if we can get rid of "WritePortableOrSerializable" method.
> ----------------------------------------------------------------------
>
>                 Key: IGNITE-1572
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1572
>             Project: Ignite
>          Issue Type: Task
>          Components: interop
>    Affects Versions: ignite-1.4
>            Reporter: Vladimir Ozerov
>            Assignee: Pavel  Tupitsyn
>            Priority: Critical
>             Fix For: ignite-1.5
>
>
> We have lots of places where "WritePortableOrSerializable" routine is invoked. It is not clear why do we need it provided that we already handle [Serializable] classes properly. 
> Looks like we are able to get rid of it safely, aren't we? Need to double-check.



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