[Nfd-dev] semantics of Transport::pause

[Davide Pesavento]

I know, I was not referring to the existing transports, hence the "what if".

On Tue, Jan 20, 2015 at 5:15 AM, Junxiao Shi
<shijunxiao at email.arizona.edu> wrote:
> Hi Davide
>
> TcpTransport and UnixTransport never need to send periodic keep-alive.
>
> Yours, Junxiao
>
>
> On Mon, Jan 19, 2015 at 9:12 PM, Davide Pesavento <davide.pesavento at lip6.fr>
> wrote:
>>
>> On Tue, Jan 20, 2015 at 4:48 AM, Alex Afanasyev <afanasev at cs.ucla.edu>
>> wrote:
>> > On pause, all pending io_service tasks (e.g., for asynchronous waiting
>> > for
>> > incoming data) need to be cancelled (but socket should be kept in open
>> > state)
>>
>> What if the underlying transport mechanism needs to send periodic
>> keep-alive packets in order to maintain the connection? (Or am I
>> misunderstanding what you mean by keeping the socket "in open state"?)
>>
>> Thanks,
>> Davide
>
>
>
> _______________________________________________
> Nfd-dev mailing list
> Nfd-dev at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>