Along with IE/Windows wininet autodial apis, there's a message (I forget the exact message ID right now though) that you can post to an invisible autodial window periodically to tell it that we are busy and to not hang up.
There is also an api in shdocvw.dll "SetQueryNetSessionCount", which increments, decrements, queries and returns the current session count, which is used by autodial to decide when to hang up. There are two aspects to autodial that can be configured via the Internet Control Panel: hang up when I'm finished or hang up when I'm idle for n minutes I have some code that does this and will see if I can't dig it up... -Abe ----- Original Message ----- > If Windoze is smart enough to autodial when some program wants to use the > internet it then should be smart enough to notice that the connection has > gone idle and do an idle time-out for hanging up. If not, then its broken. > > You can't blame the program that USES that auto-dialed connection for not > hanging up. It didn't dial, why should it hang up? Every program that might > use the internet (auto-dialled) now has to be modified to know how to hang > up the connection? What if you have two programs using the connection at > the same time, and one of them decides to hang it up? Oops. Clearly not the > right solution. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
