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-10098) .NET: TcpCommunicationSpi misses some properties of java TcpCommunicationSpi
Date Mon, 19 Nov 2018 14:33:00 GMT

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

Pavel Tupitsyn commented on IGNITE-10098:
-----------------------------------------

Looks good to me.
Merged to master: {{a198b3ff5799899690419e3c0b6306a1eaebd6e7}}.

> .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)

Mime
View raw message