[Nfd-dev] semantics of Transport::pause

[Alex Afanasyev]

These are assumptions in the library, which were based on a single machine environment where one can keep a hard state.  If we were to support something beyond local machine, pause/resume can be null operations (though it would require applications to be aware of that).

—
Alex

> On Jan 19, 2015, at 8:15 PM, 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 <mailto:davide.pesavento at lip6.fr>> wrote:
> On Tue, Jan 20, 2015 at 4:48 AM, Alex Afanasyev <afanasev at cs.ucla.edu <mailto: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
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20150119/fd344a56/attachment.html>