.If you have a session and are using the UDP transport (which should be the default in current releases) you should see the disconnect much sooner than 1800s. If you don't have a session it is trickier as there are a various timers in the system related to discovery.
What exactly is the use case you wish to solve? There is a presence facility (not surprisingly called ping) and aditional functionality in the form of a helper library called the auto-pinger, that will detect if someone is gone. So the question is: how important is it to find out that a peer you care about is no longer there? Tradeoff is of course network traffic. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of John Crispin Sent: Wednesday, January 13, 2016 5:41 AM To: Steve Kinneberg Cc: [email protected] Subject: Re: [Allseen-core] detecting remote power down On 13/01/2016 14:14, John Crispin wrote: > Hi Steve, > > i am playing with the AboutClient sample in 15.09. > void SessionLost() only gets called on an ordered shut down of a > remote device. If I just disconnect the power of the remote device I > will have a stale session that wont even be flushed after TCP timeout. > this sort of defeats the purpose of said callback if it only gets > called on some occasions but not all. > > which API do i need to use instead to find out when a session goes stale ? > > John > _______________________________________________ > Allseen-core mailing list > [email protected] > https://lists.allseenalliance.org/mailman/listinfo/allseen-core > Hi, ok, correction, alljoyn did notice after 1870 seconds. any idea how we can reduce this to something sane like 30s ? JOhn _______________________________________________ Allseen-core mailing list [email protected] https://lists.allseenalliance.org/mailman/listinfo/allseen-core _______________________________________________ Allseen-core mailing list [email protected] https://lists.allseenalliance.org/mailman/listinfo/allseen-core
