Thanks for closeStack/killSockets tip, Chipp. Would using such a
script be adviseable even in stacks which don't manual open sockets,
but which do access URLs such as FTP sites using the a command like:
get URL ftp://whatever.com; , which presumably both open and close a
socket within that one
On Monday, November 4, 2002, at 10:11 PM, Chipp Walters wrote:
for instance, I usually put the following in all my stacks:
Main stacks, I note.
I'm just developing my style and it is not clear to me what to copy to
my main stack script and what to leave in a library stack. Conflict in
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
At 10:30 am -0600 5/11/02, Chipp Walters wrote:
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
To: [EMAIL PROTECTED]
Subject: RE: Cool generic scripts...
At 10:30 am -0600 5/11/02, Chipp Walters wrote:
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
