cURL
Haxx ad
libcurl

curl's project page on SourceForge.net

Sponsors:
Haxx

cURL > Mailing List > Monthly Index > Single Mail

curl-tracker mailing list Archives

[ curl-Bugs-2153446 ] Make CURLINFO_LASTSOCKET accessible during perform

From: SourceForge.net <noreply_at_sourceforge.net>
Date: Thu, 09 Oct 2008 18:14:13 +0000

Bugs item #2153446, was opened at 2008-10-08 11:14
Message generated for change (Comment added) made by vmpdemo
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=2153446&group_id=976

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: libcurl
Group: new feature request
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: vmpdemo (vmpdemo)
Assigned to: Daniel Stenberg (bagder)
Summary: Make CURLINFO_LASTSOCKET accessible during perform

Initial Comment:
Make CURLINFO_LASTSOCKET accessible during curl_easy_perform.

The difference is that without this change, CURLINFO_LASTSOCKET is confusingly not set from the perspective of any CURLOPT_PROGRESSFUNCTION callback.

Note I'm not certain what the implication might be of removing the data->state.lastconnect setting line from the Curl_done function. Seemingly that choice was arbitrary, but I've left out changing that from my patch.

----------------------------------------------------------------------

>Comment By: vmpdemo (vmpdemo)
Date: 2008-10-09 13:14

Message:
This is mainly useful if you're NOT using CURLOPT_CONNECT_ONLY. With
CURLOPT_CONNECT_ONLY this is fairly irrelevant.

But without CURLOPT_CONNECT_ONLY, this change allows you to see the socket
in progress. In particular a HTTP request may be slow in getting a
response back, and you can now see the socket in use during that time.

----------------------------------------------------------------------

Comment By: Daniel Stenberg (bagder)
Date: 2008-10-08 16:00

Message:
It wasn't exactly arbitrary but the whole point of CURLINFO_LASTSOCKET has
been to extract the socket _after_ a compelted request, not getting it
during operations. In fact, libcurl may use more than one socket while in
progress an in this case you may also get a period in the beginning of the
request where there is no lastsocket assigned.

What's your use-case for wanting this info this early in the process? I'm
not shooting down the suggestion, just trying to get a better picture.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=2153446&group_id=976
Received on 2008-10-09

These mail archives are generated by hypermail.

donate! Page updated November 12, 2010.
web site info

File upload with ASP.NET