On 12/16/2009 12:41 PM, Philip A. Prindeville wrote:
> Can anyone interested please comment on:
>
> https://sourceforge.net/tracker/?func=detail&atid=350976&aid=2915224&group_id=976
>
>
> The premise of this ticket is that certain configuration options need to be site-wide (such as going through a proxy or a virus-checker for HTTP fetches... or in my case setting QoS policy). That is, site-wide and only site-wide: options affecting security policy or performance shouldn't be overridden by users' settings.
>
> It's also easier to deploy new settings if they are only turned on in one place, rather than in $HOME/.curlrc for hundreds or thousands of users.
>
> Lastly, there's the open question of whether this should apply to just Curl or to libcurl... there's a number of 3rd party software packages that link to libcurl (such as Asterisk) and they would need a mechanism for importing these same defaults. A site-wide defaults file solves the problem of rolling out new options when libcurl.so gets released, without having to edit, re-compile, repackage, redistribute, and reinstall all of the software packages that link with libcurl.so.
>
> Thanks,
>
> -Philip
>

Really? No one has anything at all to say on this?

Daniel? Do you have an opinion on either issue one way or another?

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2010-03-14