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 2018/11/19 14:31:00 UTC

[jira] [Updated] (IGNITE-10098) .NET: TcpCommunicationSpi misses some properties of java TcpCommunicationSpi

     [ https://issues.apache.org/jira/browse/IGNITE-10098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Tupitsyn updated IGNITE-10098:
------------------------------------
    Summary: .NET: TcpCommunicationSpi misses some properties of java TcpCommunicationSpi   (was: TcpCommunicationSpi for .NET misses some properties of java TcpCommunicationSpi )

> .NET: TcpCommunicationSpi misses some properties of java TcpCommunicationSpi 
> -----------------------------------------------------------------------------
>
>                 Key: IGNITE-10098
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10098
>             Project: Ignite
>          Issue Type: Task
>          Components: platforms
>    Affects Versions: 1.6
>            Reporter: Maxim Pudov
>            Assignee: Maxim Pudov
>            Priority: Major
>              Labels: .NET
>             Fix For: 2.8
>
>
> For example, TcpCommunicationSpi in .NET doesn't have socketWriteTimeout.
> It might be helpful to create an API parity test for TcpCommunicationSpi like DataRegionConfigurationParityTest.cs for DataRegionConfiguration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)