On Fre 21.12.2007 11:32, Daniel Stenberg wrote:
> On Thu, 20 Dec 2007, Nathaniel McCallum wrote:
>
>>> Although, making a JavaScript interpreter a prerequisite turns curl
>>> into a pretty heavy-weight app.
>>
>> This is not how libproxy works. libproxy has no dependencies of its
>> own. Currently its size is 35K, but we are looking to shrink it, not
>> grow it. All functionality is added via plugins at runtime.
>
> Well run-time or not doesn't really matter IMHO, it's just a question
> of which loader that loads the code. If you want a somewhat complete
> proxy-detection you _need_ to handle PAC and to handle PAC you need a
> javascript interpreter and more, and that is a significant amount of
> code.
>
> And with PAC you also add HTTP round-trips, DNS lookups and more for
> each use.

http://code.google.com/p/pacparser/

---
pacparser is a C library to parse PAC (proxy auto-config) files. PAC
files (implemented in JavaScript) are a proxy configuration method for
web access. Using them, browsers can be configured to use different
proxy servers for different URLs, source IP addresses, protocols
etc. PAC files can also be used for a highly available proxy setup as
you can specify more than one proxy server using them.
.
.
.
---
Maybe your lib add this lib ;-)
Cheers
Aleks