Salut and Suspend/Resume issues

[Ricardo Carrano]

Benjamin, Yanni,

If I understand you correctly, I believe that, in the end, what you are
proposing is what the avahi should do normally.
It keeps soft state data about the neighbours.

On Feb 19, 2008 3:32 PM, Giannis Galanis <giannisgalanis at gmail.com> wrote:

> For the protocol to be healthy,
>
> not only you have to wake every 10min to send your request,
> but you have to be awake to receive the others' requests.
>
> These are again 10min, but have different offsets. Thats why I believe the
> only way would be to have 10off - 10on.
>
> Still, due to bug 5501, if you miss a single request, u are prone to be
> deleted right away.
>
> So 10ff-10on might not work either.
>
> In fact the although the requests are every 10min, the icon will hold for
> 30min in total until it is deleted.
> Bug 5501, however, will delete the entry if within the timeframe, a new
> host arrives.
>
>
>
>
> On Feb 19, 2008 1:19 PM, Benjamin M. Schwartz <bmschwar at fas.harvard.edu>
> wrote:
>
> > On Tue, 2008-02-19 at 13:11 -0500, Giannis Galanis wrote:
> >
> > >
> > > The wakeup required is T minutes for every T minutes.
> > > Actually you would need to be awake  for >T  minutes
> > > and suspended for <T minutes to be sure u are ok.
> > >
> > > So for T=10min, as in this case:
> > > 9off, 11on, 9 off, 11on
> > >
> > > but this is not very effective in terms of suspend/resume
> >
> > I meant to imply that this would work only if the wireless hardware
> > wakes up the system for every broadcast.
> >
> > --Ben
> >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/devel/attachments/20080219/aba0fabc/attachment.html>