[
https://issues.apache.org/jira/browse/IGNITE-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647751#comment-14647751
]
Nikolay Tikhonov commented on IGNITE-1169:
------------------------------------------
I got the following progress:
* Changed future to closure.
* Added sendWithAck methods on GridIoManager.
* Added tests.
> Need to add TcpCommunicationSpi.sendWithAck
> -------------------------------------------
>
> Key: IGNITE-1169
> URL: https://issues.apache.org/jira/browse/IGNITE-1169
> Project: Ignite
> Issue Type: New Feature
> Reporter: Yakov Zhdanov
> Assignee: Nikolay Tikhonov
> Priority: Critical
> Attachments: ignite-1169-1.patch
>
>
> Communication uses internal acks to manage connection recovery queues in
> order not to miss messages on connection problems.
> We need to add TcpCommunicationSpi.sendWithAck that returns future which gets
> completed when node sends communication ack back.
> Use case:
> Sometimes we need to send messages and know for sure that message has been
> delivered (not processed - this is stronger requirement). So, we can use
> communication ack not to introduce top-level protocol acks. This can be used,
> for example, to make sure that client has received continuous query
> notification.
> Brief list of changes:
> * TcpCommunicationSpi - add sendWithAck() method, implement notification
> logic on top of existing acks
> * IoManager - add ability to send ordered and unordered messages with ack and
> get notification on peer receiving the message.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
