On Thu, 14 Oct 2004, Karthik Ramakrishnan wrote:

(CC'ing the curl-library list)

> Are there any plans to enhance cURL to provide more than just the last used
> URL when we call the "curl_easy_getinfo" API.

The "plans", as far as there are any, are summarized in the TODO and
KNOWN_BUGS document. But we generally tend to fix things we come to think of
is missing or not working when we fall over them.

I personally don't see the benefit of your suggested option.

> Ideally, an API which returns all the URL's (where number of URL's is
> specified by CURLOPT_MAXCONNECTS) will help applications using cURL in a
> multi threaded environment - where each thread has its own cURL handle in
> intelligently selecting the right thread there by selecting the right handle
> to do the work.

You mean you want to figure out if one of your existing CURL handles has a
connection open to a host you want to fetch a URL from?

EFFECTIVE_URL isn't gonna provide that answer, since the connection may very
well have been disconnected.

-- 
      Daniel Stenberg -- http://curl.haxx.se -- http://daniel.haxx.se
       Dedicated custom curl help for hire: http://haxx.se/curl.html