curl-library

From: Serge van den Broek <SVandenbroek_at_isabel.be> Date: Fri, 9 Sep 2005 16:33:28 +0200 · >> see around line 240 in include/curl/multi.h for the

--
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html
------------------------------
Message: 2
Date: Thu, 8 Sep 2005 18:27:45 +0200
From: Fr?d?ric Sarron <fred.sarron_at_gmail.com>
Subject: SOCKS4 support ?
To: curl-library_at_cool.haxx.se
Message-ID: <cc06de410509080927522e828b_at_mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi everyone,
I dont know if it's is the exact right place to ask this question, pardon me 
if not.
I know socks4 is not currently supported, it was suggested in the FAQ and 
was confirmed to me by testing.
Is socks4 support a wanted feature and will it be scheduled for future 
release ?
thanks by advance,
Fred Sarron
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://cool.haxx.se/pipermail/curl-library/attachments/20050908/b89e8020/attachment.html
------------------------------
Message: 3
Date: Thu, 8 Sep 2005 22:28:58 +0200 (CEST)
From: Daniel Stenberg <daniel-curl_at_haxx.se>
Subject: Re: SOCKS4 support ?
To: libcurl development <curl-library_at_cool.haxx.se>
Message-ID: <Pine.LNX.4.63.0509082225260.9008_at_yvahk3.pbagnpgbe.fr>
Content-Type: text/plain; charset="iso-8859-1"
On Thu, 8 Sep 2005, Fr�d�ric Sarron wrote:
> Is socks4 support a wanted feature and will it be scheduled for future 
> release ?
If someone brings patches that add sock4 support and the code is clean and 
neat, then I wouldn't mind adding support for it.
But judging from how the existing socks5 support lacks and is inadequate, it 
doesn't seem to be very many people out there who wants socks support.
I don't know of anyone who plans to add this, and I certainly won't unless 
someone convinces me with the proper monetary arguments! ;-)
-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html
------------------------------
Message: 4
Date: Fri, 9 Sep 2005 00:53:40 +0200
From: Alexander Lazic <al-curllibrary_at_none.at>
Subject: Re: curl_multi_fdset alternatives
To: libcurl development <curl-library_at_cool.haxx.se>
Message-ID: <20050908225340.GA31797_at_none.at>
Content-Type: text/plain; charset=us-ascii; format=flowed
On Don 08.09.2005 14:28, Daniel Stenberg wrote:
>On Wed, 7 Sep 2005, Alexander Lazic wrote:
>
>>Looks very nice ;-) How can i help you to implement these idea?
>
>You tell me where I find a few extra hours per day for a month or so!
>
>If I'm very lucky, I get funded to do these changes later this year.
;-)
>>CURLMcode curl_multi_socket(CURLM *multi_handle,
>>                           curl_socket_t s,
>>                           CURL *easy,
>>                           curl_socket_callback callback,
>>                           void *userp); /* passed to callback */
>>
>>do i understand this right that the 'app' make the
>>socket()/fctl(..$NONBLOCK..) calls and
>>curl_multi_init()/curl_easy_init() and then call the
>>curl_multi_socket, right?
>
>The socket() calls would be for the applications own use, right?
I think so.
>They can be created, used and waited for togather with the ones
>curl_multi_socket() provides.
But the app feed the curl_multi_socket() thefore curl_multi_socket()
should only have the sockets from the app.
I think this is the major problem because some functions make their own
socket()/connect() calls.
>curl_multi_socket() calls the callback to inform the application about
>what sockets it uses and what actions to wait for on them. It also
>calls the callback when sockets are removed or if there's a change of
>action to wait for.
I think i have understood this, hopefully.
>The app should then wait for action on all sockets libcurl has told it
>about (and of course its own set of file descriptors).
Yes and the one which the libcurl create by it self also!
>A main difference from today is that you'd tell curl_multi_socket()
>exactly what socket that had action on it so that it wouldn't have to
>check all its sockets for that but only work on the actual socket that
>needs attention.
I think this is a major redesign for libcurl, isn't it?
I have looked into 'curl-7.14.1/lib/transfer.c => Curl_readwrite()' which
is called by 'curl-7.14.1/lib/multi.c => curl_multi_perform()'.
Have i the right point of view from your site?
Now i understand what you have mean with the extra time.
Greetings
al ;-)
------------------------------
Message: 5
Date: Fri, 09 Sep 2005 09:14:47 +0530
From: Rajneesh <r.khanna_at_samsung.com>
Subject: Re: Port for VxWorks
To: libcurl development <curl-library_at_cool.haxx.se>
Message-ID: <00dc01c5b4f0$d42b37c0$e25c6c6b_at_Rajneesh>
Content-Type: text/plain; format=flowed; charset=iso-8859-1;
	reply-type=response
Hi Daniel,
              Sorry for not replying - was busy with meetings thereafter. U 
know how these company meetings are ...huh!! :) Well, thanx for answers.
I shall have more questions - compiling and linking etc. Later ofcourse !!
Sure, i shall let you know once the port is ready and can release my changes 
. That should really be helpful to others like me.
Thanx once again.
Cheers,
Rajneesh
----- Original Message ----- 
From: "Daniel Stenberg" <daniel-curl_at_haxx.se>
To: "libcurl development" <curl-library_at_cool.haxx.se>
Sent: Thursday, September 08, 2005 2:25 PM
Subject: Re: Port for VxWorks
> On Thu, 8 Sep 2005, Rajneesh wrote:
>
>> 1. I know OpenSSL is for Linux primarily, but how easy would it be if we 
>> plan to port it to VxWorks. I mean is there any POSIX layer/wrapper that 
>> can help me in porting SSL to VxWorks ?
>
> OpenSSL is pretty portable, AFAIK. But I would assume that it too relies 
> pretty much on a POSIX layer. I figure you need to consult the OpenSSL 
> sources or ask the OpenSSL developers to get insights in how you'd best 
> approach that.
>
>> 2. I have made my own config-vxworks.h file from the sample OSes config 
>> files that are there in curl-7.14.1/lib folder. Although i am having some 
>> trouble compiling the library, i think i can remove the errors.My 
>> question is have i started correctly ?
>
> I think you have. If you make sure to #ifdef your changes in the existing 
> tradition, we can then later incorporate your changes back and have 
> libcurl compilable for VxWorks out-of-the-box in the future...
>
>> 3. Isn't OpenSSL bundled with curl-7.14.1 available on the website ?
>
> OpenSSL is not bundled with curl. http://www.openssl.org/ is the place to 
> look for the OpenSSL package.
>
> -- 
>  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html
>
> 
------------------------------
Message: 6
Date: Fri, 9 Sep 2005 10:31:10 +0200 (CEST)
From: Daniel Stenberg <daniel-curl_at_haxx.se>
Subject: Re: curl_multi_fdset alternatives
To: libcurl development <curl-library_at_cool.haxx.se>
Message-ID: <Pine.LNX.4.63.0509091013480.18223_at_yvahk3.pbagnpgbe.fr>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
On Fri, 9 Sep 2005, Alexander Lazic wrote:
>> They can be created, used and waited for togather with the ones 
>> curl_multi_socket() provides.
>
> But the app feed the curl_multi_socket() thefore curl_multi_socket() should 
> only have the sockets from the app.
I don't understand what you mean. curl_multi_socket() will tell your app what 
sockets it uses and then your app waits for actions on the sockets. libcurl's 
and your own. Using the method of your choice.
It should make it possible to use any high-performance lib or method.
It should make libcurl a huge step closer to dealing with the c10k problem.
Of course, nothing of this is carved in stone yet so we can still tune how 
these functions should behave.
> I think this is the major problem because some functions make their own 
> socket()/connect() calls.
The application's sockets, connects etc are not a concern of libcurl. The 
application deals with its own sockets.
>> A main difference from today is that you'd tell curl_multi_socket()
>> exactly what socket that had action on it so that it wouldn't have to
>> check all its sockets for that but only work on the actual socket that
>> needs attention.
>
> I think this is a major redesign for libcurl, isn't it?
It isn't really a redesign, but it is a pretty big change yes.
Hopefully, it should make libcurl a lot better performing when you use it for 
huge amount of simultanoues transfers.
This fix, together with added HTTP pipeling support, ought to make libcurl 
outperform most of the competition.
> Now i understand what you have mean with the extra time.
:-)
With a full time job and a real-life family, the day just don't have enough 
hours.
I expect this API to get added eventually, but I can't tell when. Hopefully 
there will show up a company that finds out it wants this added that pays 
someone to make the changes.
I'll appreciate help of course.
-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html
------------------------------
_______________________________________________
curl-library mailing list
curl-library_at_cool.haxx.se
http://cool.haxx.se/mailman/listinfo/curl-library
End of curl-library Digest, Vol 20, Issue 19
********************************************
 
Serge Vandenbroek
Analyst Programmer
E-mail : SVandenbroek_at_isabel.be
Tel   : +32 (0)2 545.17.67
Fax  : +32 (0)2 545.17.19
 
Isabel NV/S.A. 
Keizerinlaan 13/15 Bld de l'Imp�ratrice 
1000 Bruxelles /Brussel
RPR Bruxelles /RPM Brussel: BE 0455 530 509
--------------------------------------------------------
Need assistance? 
Get help from Isabel Web Support 
www.isabel.be/support
--------------------------------------------------------
DISCLAIMER : Confidential information may be contained in this message and it may be legally privileged. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer does not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of Isabel shall be understood as neither given nor endorsed by it. Messages and attachments are swept by a virusscanner. If this message contains password-protected attachments, the files have not been scanned for viruses by the Isabel mail domain.

curl-library

Error recompiling curl with more recent version