On Tue Jan 23 15:15:38 2007, Kalle Valo wrote:
> Shuts down the association or the physical interface? (And I know,
> I've suddenly switched to OSI-speak to avoid the word "connection"
> here)
>
> And is this done merely if associations are idle, or only if
there are
> no current associations?
Sorry, I don't quite understand your terms here.
Connection can mean the act of connecting, or the result of one, and
it might mean WiFi or TCP. Associations, on the other hand, are what
TCP (or another transport protocol) provides.
But basically when idle timer triggers, the WLAN or BT DUN
connection
is disconnected similarly as user would have clicked disconnect
button
in Connection Manager or in Connection Status Bar Applet.
Anyways, the default is to have idle timer enabled only for BT DUN
Circuit Switched Data connections (ie. data calls), which makes
sense
because they are usually charged per minute. WLAN and BT DUN Packet
Switched connections do _not_ have idle timeout set by default.
That's fine, then.
Hopefully this makes things a bit more clear. Do you still see a
problem with our idle timer implementation?
Yes, that's a lot clearer, and no, I don't think there's any problems
there.
Dave.
--
Dave Cridland - mailto:[EMAIL PROTECTED] - xmpp:[EMAIL PROTECTED]
- acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
- http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
_______________________________________________
maemo-users mailing list
maemo-users@maemo.org
https://maemo.org/mailman/listinfo/maemo-users
