ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-10619) Add support for ReadableByteChannel, WritableByteChannel over CommunicationSpi
Date Mon, 10 Dec 2018 11:08:00 GMT

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

ASF GitHub Bot commented on IGNITE-10619:

GitHub user Mmuzaf opened a pull request:


    IGNITE-10619: CommunicationSpi support channels initial commit

    - GridNioServer supports channel creation from GridNioSession
    - rework createTcpClient method
    - new GridIoManager channel creation listener
    - updated HandshakeMessage2 to support new connections
    - new connection Builder'ы

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

    $ git pull https://github.com/Mmuzaf/ignite ignite-10619

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


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

    This closes #5619
commit ae7e5f6e10b23caf98830e349286bcf4ea059cff
Author: Maxim Muzafarov <maxmuzaf@...>
Date:   2018-12-10T11:01:44Z

    IGNITE-10619: CommunicationSpi support channels initial commit


> Add support for ReadableByteChannel, WritableByteChannel over CommunicationSpi
> ------------------------------------------------------------------------------
>                 Key: IGNITE-10619
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10619
>             Project: Ignite
>          Issue Type: Sub-task
>            Reporter: Maxim Muzafarov
>            Assignee: Maxim Muzafarov
>            Priority: Major
> To benefit from zero copy we must delegate the file transferring to FileChannel#transferTo(long,
long, java.nio.channels.WritableByteChannel) because the fast path of transferTo method is
only executed if the destination buffer inherits from an internal JDK class.
> The {{CommunicationSpi}} needs to support pipe connections between two nodes;
> * The WritableByteChannel needs to be accessed on the supplier side;
> * The ReadableByteChannel needs to be read on the demander side;
> * The CommunicationListener must be extended to respond on new incoming pipe connections;

This message was sent by Atlassian JIRA

View raw message