FWIW, since this is in fact part of libURL, it is possible to edit the scripts in question and change their behavior if either the need is urgent or it doesn't get officially changed.
If you truly want the socket immediately closed, is there any reason why you can't check for it and close it yourself after the transfer is complete? i.e.
repeat until the openSockets is empty
close socket (line 1 of the openSockets)
end repeat
HTH,
Brian
I believe you. But the behavior is intentional. By default, the
libUrl script doesn't close the socket after completing a request.
This allows re-use of the same socket which is useful if you are
making a series of requests to the same server, and is in line with
the HTTP 1.1 spec. (The socket will eventually get closed by the
server.)
------------------------------
Brian Yennie
Chief Technology Officer
QLD Learning, LLC
www.QLDLearning.com
PH: (904)-997-0212
EMAIL: [EMAIL PROTECTED]
-------------------------------
