curl-library
RE: curl-library Digest, Vol 38, Issue 19
Date: Thu, 9 Oct 2008 13:03:01 -0400
Thanks, Colin. That did the trick.
Cheers,
Fred Wurtz
-----Original Message-----
From: curl-library-bounces_at_cool.haxx.se
[mailto:curl-library-bounces_at_cool.haxx.se] On Behalf Of
curl-library-request_at_cool.haxx.se
Sent: Thursday, October 09, 2008 6:00 AM
To: curl-library_at_cool.haxx.se
Subject: curl-library Digest, Vol 38, Issue 19
Send curl-library mailing list submissions to
curl-library_at_cool.haxx.se
To subscribe or unsubscribe via the World Wide Web, visit
http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-library
or, via email, send a message with subject or body 'help' to
curl-library-request_at_cool.haxx.se
You can reach the person managing the list at
curl-library-owner_at_cool.haxx.se
When replying, please edit your Subject line so it is more specific than
"Re: Contents of curl-library digest..."
Today's Topics:
1. Re: fatter without benefits (was Re: [Patch] Disable multi
API support) (Daniel Stenberg)
2. Re: cannot connect to server in a subthread (Daniel Stenberg)
3. Re: fatter without benefits (was Re: [Patch] Disable multi
API support) (Mohun Biswas)
4. RE: cannot connect to server in a subthread (Patrick Monnerat)
5. Re: setopt(CURLOPT_*,$curlopthash->{$option}) apparently
doesn't work (Daniel Stenberg)
6. Correction to online documentation (Carlos Alloatti)
7. Curl on Symbian OS (Pavan JP)
8. Re: Curl on Symbian OS (Dan Fandrich)
9. Re: setopt(CURLOPT_*,$curlopthash->{$option}) apparently
doesn't work (Colin Hogben)
----------------------------------------------------------------------
Message: 1
Date: Wed, 8 Oct 2008 19:55:29 +0200 (CEST)
From: Daniel Stenberg <daniel_at_haxx.se>
Subject: Re: fatter without benefits (was Re: [Patch] Disable multi
API support)
To: libcurl development <curl-library_at_cool.haxx.se>
Message-ID: <alpine.LRH.1.10.0810081403500.27452_at_yvahk3.pbagnpgbe.fr>
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
On Wed, 8 Oct 2008, Daniel Egger wrote:
> The only features though we will ever use are:
> - HTTP 1.0/1.1
> - FTP
> - FILE
> synchronous downloads with range/continuation possibilities. I will
> continue to strive to get those features in the smallest possible
> package because I'm just not interested in the rest.
As I've already explained, I'm also interested in supporting that.
> Unfortunately those features were already present since 7.17.3 so
> indeed there are no benefits in the library but lots of object size
> bloat. The only thing I get by upgrading are security fixes
That's simply not true. There are also a large range of bug fixes for
various aspects of those mentioned protocols.
> If curl wants to suite as many needs as possible one of the main goals
> should be to keep it as small as possible and as modular as possible.
I don't want it to fit "as many needs as possible". I want it to do file
transfers and just about anything that is related to that and the
protocols it supports. Each new thing is considered when people bring
them.
I also consider options to make it "as possible and as modular as
possible" as you know by now.
In the end I know that I am the guy who is going to be around in five
years and then I want to be able to still have maintainable code and I
want people to be able to write patches rather easy over time without
hitting unnecessary hurdles. So I try to set some requirements of what I
want to go into the code.
You're free to argue for your case and explain to me how my reasoning is
wrong and possibly I could reconsider, but saying that all we do is
"bloat" is not the smoothest way forward to do that.
You whining about your spent time (that seems to have been paid by a
company) is also mostly amusing since I've spent 10 years (of spare
time) on this project.
> I for one could even imagine splitting the library in half for
> easy/multi interface because the multi interface is far to
> generic/powerful to be of any use for many users.
I think such a split could be useful, but also a bit in the reverse
direction of what I'm considering. I'm more in favour of making
_everything_ internally be the multi interface, adn then have the easy
interface as a wrapper on top of that. It will simplify the code with
only having one actual way of functioning internally.
Of course we're not near this situation and I'm not in a situation in my
life atm where I can push development on this either way.
-- / daniel.haxx.se ------------------------------ Message: 2 Date: Wed, 8 Oct 2008 20:00:10 +0200 (CEST) From: Daniel Stenberg <daniel_at_haxx.se> Subject: Re: cannot connect to server in a subthread To: libcurl development <curl-library_at_cool.haxx.se> Message-ID: <alpine.LRH.1.10.0810081957340.21045_at_yvahk3.pbagnpgbe.fr> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed On Wed, 8 Oct 2008, Michael Helmich wrote: > I'm having a very strange problem when using curl in a multithreaded > program on Solaris 9. When i'm accessing a certain server only in a > subthread, > curl_easy_perform() returns 7 ("Couldn't connect to server"), whereas > when i'm accessing the same server only in the main thread (or first > in the main thread and afterwards in the subthread), everything works > fine. Connections to other servers work in a subthread as well as in > the main thread. What could be the cause of such a behavior? I've not seen or heard anyone report this kind of problem before, and I know I've done that thing on Linux many times with no troubles. I think it might suggest it being a Solaris specific problem. Have you tried the Solaris threads API and seen if that produces the same problem? I must admit I haven't played on a Solaris box in a while so I've not tried this approach myself on any Solaris version. -- / daniel.haxx.se ------------------------------ Message: 3 Date: Wed, 08 Oct 2008 14:42:59 -0400 From: Mohun Biswas <m_biswas_at_mailinator.com> Subject: Re: fatter without benefits (was Re: [Patch] Disable multi API support) To: curl-library_at_cool.haxx.se Message-ID: <gciuvk$u6m$1_at_ger.gmane.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Daniel Stenberg wrote: > You whining about your spent time (that seems to have been paid by a > company) is also mostly amusing since I've spent 10 years (of spare > time) on this project. I'm not involved in this disagreement but I do want to say that I think it's unfair for you to accuse Daniel Egger of "whining". You (arguably) called him selfish; he was defending himself against that by pointing out that he's contributed a lot of time. I don't call that whining. ISTM that "selfish" contributors are the ones who just agitate for someone else to do the work, or who drop off a sloppy patch and nothing else. The good ones follow coding conventions and provide parallel patches for documentation and test suite. Mr Egger was just pointing out that he's been in the latter category and from my memory that's true. Ironically, if you only took contributions from unselfish people libcurl would be a very slim library indeed. Most people contribute a feature because they have a use for that feature. In fact, isn't that the driving principle of open-source software? I think if you take a deep breath and re-read the thread you'll see that calumny, on either side, is unnecessary. MB ------------------------------ Message: 4 Date: Wed, 8 Oct 2008 21:28:59 +0200 From: "Patrick Monnerat" <Patrick.Monnerat_at_datasphere.ch> Subject: RE: cannot connect to server in a subthread To: "libcurl development" <curl-library_at_cool.haxx.se> Message-ID: <AB5E58B87EB73C46A38073D8F459F11335BD23_at_dataspheresrv01> Content-Type: text/plain; charset="us-ascii" Michael Helmich wrote: > I'm having a very strange problem when using curl in a multithreaded > program on Solaris 9. When i'm accessing a certain server only in a > subthread, > curl_easy_perform() returns 7 ("Couldn't connect to server"), whereas > when i'm accessing the same server only in the main thread (or first > in the main thread and afterwards in the subthread), everything works > fine. Connections to other servers work in a subthread as well as in > the main thread. What could be the cause of such a behavior? If it can help: I once had such a problem on Solaris, because I did not compile with "-DREENTRANT"... ------------------------------ Message: 5 Date: Wed, 8 Oct 2008 23:25:06 +0200 (CEST) From: Daniel Stenberg <daniel_at_haxx.se> Subject: Re: setopt(CURLOPT_*,$curlopthash->{$option}) apparently doesn't work To: libcurl development <curl-library_at_cool.haxx.se> Message-ID: <alpine.LRH.1.10.0810082323050.28138_at_yvahk3.pbagnpgbe.fr> Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII On Wed, 8 Oct 2008, Wurtz, Frederick (GE, Research, consultant) wrote: > foreach my $option (keys(%$curlopthash)) { > $curl->setopt($option,$curlopthash->{$option}); ... > Does somone have an idea why I would have to hard code the > $curl-setopt(CURLOPT_*, <value>) calls locally, even when the > passed-in hash is providing the same values? Unfortunately I don't think we have many perl binding users around here so I'm not sure you'll get a fine answer. Even worse: I don't even know of a better place where such people are more likely to be found! ;-( I hope someone proves me wrong. -- / daniel.haxx.se ------------------------------ Message: 6 Date: Wed, 8 Oct 2008 22:40:32 -0300 From: "Carlos Alloatti" <calloatti_at_gmail.com> Subject: Correction to online documentation To: "libcurl development" <curl-library_at_cool.haxx.se> Message-ID: <1b6c15ea0810081840jceea1c4pece527566bc67080_at_mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 In http://curl.haxx.se/libcurl/c/curl_easy_setopt.html where it says: CURLOPT_FTPSSLAUTH Pass a long using one of the values from below, to alter how libcurl issues "AUTH TLS" or "AUTH SSL" when FTP over SSL is activated (see CURLOPT_FTP_SSL). (Added in 7.12.2) It should say: CURLOPT_FTPSSLAUTH Pass a long using one of the values from below, to alter how libcurl issues "AUTH TLS" or "AUTH SSL" when FTP over SSL is activated (see CURLOPT_USE_SSL). (Added in 7.12.2) -- Carlos Alloatti ------------------------------ Message: 7 Date: Wed, 8 Oct 2008 19:16:51 -0700 (PDT) From: Pavan JP <pavan_jp_at_yahoo.com> Subject: Curl on Symbian OS To: curl-library_at_cool.haxx.se Message-ID: <996687.55902.qm_at_web56104.mail.re3.yahoo.com> Content-Type: text/plain; charset="us-ascii" Hi, I would like to know if both HTTP and HTTPS are supported on Symbian OS. Readme file has information about the SSL/TLS, LDAP, SCP or SFTP URLs protocols not supported currently but I would like to know if HTTPS is supported or not. Thanks Pavan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://cool.haxx.se/pipermail/curl-library/attachments/20081008/cfe686e f/attachment.html> ------------------------------ Message: 8 Date: Wed, 8 Oct 2008 19:54:33 -0700 From: Dan Fandrich <dan_at_coneharvesters.com> Subject: Re: Curl on Symbian OS To: curl-library_at_cool.haxx.se Message-ID: <20081009025432.GA14005_at_coneharvesters.com> Content-Type: text/plain; charset=us-ascii On Wed, Oct 08, 2008 at 07:16:51PM -0700, Pavan JP wrote: > I would like to know if both HTTP and HTTPS are supported on Symbian OS. Readme > file has information about the SSL/TLS, LDAP, SCP or SFTP URLs protocols not > supported currently but I would like to know if HTTPS is supported or not. They are not currently supported (HTTPS requires SSL/TLS). If someone ports any of the supported SSL/TLS libraries to Symbian then then it should be straightforward to get it working. I haven't looked at the Symbian SSL libraries to see how feasible it would be to add native support for them in curl. >>> Dan -- http://www.MoveAnnouncer.com The web change of address service Let webmasters know that your web site has moved ------------------------------ Message: 9 Date: Thu, 09 Oct 2008 10:20:10 +0100 From: Colin Hogben <curl_at_pythontech.co.uk> Subject: Re: setopt(CURLOPT_*,$curlopthash->{$option}) apparently doesn't work To: libcurl development <curl-library_at_cool.haxx.se> Message-ID: <48EDCCCA.9010104_at_pythontech.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Wurtz, Frederick (GE, Research, consultant) wrote: > > %curlopthash = ( > CURLOPT_URL => $url, > CURLOPT_PROXY => "", > ... > > foreach my $option (keys(%$curlopthash)) { > $curl->setopt($option,$curlopthash->{$option}); > } > I'm familiar with curl and perl (though not the two together before) and I think I see the problem > > I've verified that $option is, in each case the correct "CURLOPT_*" > string and that $curlopthash->{$option} contains the correct values > It is not a string you want here, but the integer equivalent of the option. CURLOPT_URL etc. are defined as constants, equivalent to sub CURLOPT_URL {10000+2} $ perl -e 'use WWW::Curl::Easy; print CURLOPT_URL' 10002 Perl treats the bare token before '=>' as a string. Compare: $ perl -e 'use WWW::Curl::Easy; %x=(CURLOPT_URL=>'foo'); print join(" ",%x);' CURLOPT_URL foo $ perl -e 'use WWW::Curl::Easy; %x=(CURLOPT_URL,'foo'); print join(" ",%x);' 10002 foo Similar magic happens between curlies: gen-off-27:~/Incoming/WWW-Curl-3.12 $ perl -e 'use WWW::Curl::Easy; $x{CURLOPT_URL}='foo'; print join(" ",%x);' CURLOPT_URL foo $ perl -e 'use WWW::Curl::Easy; $x{(CURLOPT_URL)}='foo'; print join(" ",%x);' 10002 foo Hope this helps -- Colin Hogben ------------------------------ _______________________________________________ curl-library mailing list curl-library_at_cool.haxx.se http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-library End of curl-library Digest, Vol 38, Issue 19 ********************************************Received on 2008-10-09