Information générale
Catégorie:
Applications Internet
Titre:
Quirks with WININET API routines
Two issues involved with dialup networking connections and WININET:
1) Using InternetAttemptConnect() to establish dialup connection (system is configured with IE5) works okay when the connection is configured to dial without user intervention; if it isn't, after the user presses the connect button and the connection is established, the connect dialog reappears and the InternetAttemptConnect() call will not complete until the user selects Cancel (when this is done, the connection is still maintained).
2) After establishing the connection, I use FTP to either get or send a file to a FTP site. This works fine. If I then use InternetAutodialHangup(0) to disconnect from the ISP, it may or may not disconnect. If it does not disconnect, subsequent uses of InternetAttemptConnect will fail. Although I am closing both the FTP and Internet handles prior to hanging up, I suspect that there is an incomplete operation that is stopping the hangup from taking place. My problem is that I cannot figure out a way to determine if any operations are incomplete, so that I can wait until they do complete.
I know there must be a way to alleviate these two quirks, because they do not happen with IE or if I establish the connection by double-clicking on the DUN connectoid and hangup by right-clicking on the sytem tray icon and selecting "Disconnect".
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement