On Feb 19, 2008 4:10 PM, Ricardo Carrano <[EMAIL PROTECTED]> wrote: > Yanni, > > > > > Did a use it otherwise? Because of the effects of xmas tree, the timeout > > for a failed XO until it's icon is removed is 10-30min. > > > > I am talking about the time it takes for an avahi entry to expire. For > what you said, is 10 minutes. >
Oh ok. This is not 10min. Avahi checks every 10min that its peers are alive. An active entry will never expire A "failed" entry will naturally expire in an additional 20min(30 in total). BUT, it can expire instantly due to xmas tree bug(5501) > > > > Ricardo, do you have anwers to the questions I posted before? : > > > > Let's see: > > > > 1. When a XO resumes, does it send any notification via avahi, that it > > is back? Because if it doesnt, then other XOs that have cleared it from > > their lists, they will never search for it. > > > > I believe there is no "I am back" notification different than the normal > way presence information is exchanged by the protocol. > If not, then we have a problem. The other XOs will never know it is here, so they will never search for it. I think the "are u alive" request is destination specific. I will do some sniffing and find out. > > > > > 2. Every scans the network every 10min, to check whether its avahi peers > > are alive, in multicast packets. Do these packets include the address of the > > peers/targets? I think they do, unless i am very confused. Couldn't we > > awake/resume the target XO when it receives these specific packets? > > > > That's the point. Mdns is multicast and the XOs, when suspended, don't > listen to multicast frames. > > The suspended XO can be setup to wake up by multicast packets. This is technically possible afaik
_______________________________________________ Devel mailing list [email protected] http://lists.laptop.org/listinfo/devel
