> Guys,
>
> I have updated the ticket - added a bit more details to description.
>
> Atri, this ticket has already been picked up =)).
>
> --Yakov
>
> 2015-07-29 15:48 GMT+03:00 Atri Sharma <
[hidden email]>:
>
> > Just trying to identify if this is something I can do over the weekend :)
> >
> > On Wed, Jul 29, 2015 at 2:11 PM, Dmitriy Setrakyan <
>
[hidden email]>
> > wrote:
> >
> > > On Tue, Jul 28, 2015 at 11:43 PM, Atri Sharma <
[hidden email]>
> > wrote:
> > >
> > > > How difficult is it to implement this please?
> > > >
> > >
> > > Atri, I do agree with you. The ticket description should have a list of
> > > classes that need to be updated and some design thoughts, including
> > > explanation of why this functionality is needed.
> > >
> > >
> > >
> > > > On 29 Jul 2015 12:12, "Yakov Zhdanov (JIRA)" <
[hidden email]>
> wrote:
> > > >
> > > > > Yakov Zhdanov created IGNITE-1169:
> > > > > -------------------------------------
> > > > >
> > > > > Summary: 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
> > > > > Priority: Critical
> > > > >
> > > > >
> > > > > 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.
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > This message was sent by Atlassian JIRA
> > > > > (v6.3.4#6332)
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > Regards,
> >
> > Atri
> > *l'apprenant*
> >
>
Locked
