cURL / Mailing Lists / curl-library / Single Mail


Re: Using CURLOPT_CONNECT_ONLY option in multi interface

From: Gokhan Sengun <>
Date: Tue, 18 Oct 2011 21:51:57 +0300

> I don't exactly remember when or why we did that change, as I'm not really
> aware of any users who use CURLOPT_CONNECT_ONLY with the multi interface. I
> can see how your change is necessary but I'm just a little concerned that
> just skipping over a lot of states like that might leave something behind
> that shouldn't be left...

I am recently getting familiar with the libcurl. I suggested the first idea
that came into the mind, let me take a deeper look to see what would better
suit in this case.

> Do all test cases still run fine with this change?

I have not run the test cases from the library. Testing with my code, as far
as FTP is concerned, it looks fine. No memory or any other resource leaks.
The easy handle could be re-used over several times.

> Would you be able to work on writing a new test case that uses exactly this
> feature with the multi interface so that we can make sure that it works fine
> and will remain working fine in the future?

I would be glad writing the test case but first I need some time to get more
familiar with the project, writing the test case, using sample data, running
tests, etc. :-)

Which protocols should be included in the test? Would FTP, HTTP and SMTP

it is twice as difficult to debug a program as to write it. Therefore, if
you put all of your creativity and effort into writing the program, you are
not smart enough to debug it.

List admin:
Received on 2011-10-18