At 10:30 am -0600 5/11/02, Chipp Walters wrote:
It can. :)Brad,Some of the commands in libURL are asychronous. So it is possible to issue a command and then continue woriking in RR. In these cases, killsockets would help if one was to quit before a command was finishing executing. Course, I'm not sure RR/MC doesn't automatically kill sockets when quitting (??) I have built some of my own socket protocols for file transfer and seem to remember having some problem with a 'residual' effect after quitting a program with sockets open...that's why I use the killsockets on close stack script. It can't hurt.
closeStack isn't necessarily the same as quitting, for example when you have multiple windows. Closing all open sockets while libUrl is doing something is not a good idea. It shouldn't harm if you really are quitting, but if say your closeStack handler ran when a status window closed during a download, you could be in trouble. On shutdown would be a better place to do this.
Cheers
Dave
_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution
