On Jan 25, 2008 4:58 PM, Daniel Stenberg <daniel_at_haxx.se> wrote:
> On Fri, 25 Jan 2008, Manu Garg wrote:
>
> > IMO, libproxy and pacparser are quite different. libproxy tries to identify
> > proxy automagically which doesn't go well with integrating it with anything.
> > pacparser doesn't do any magic. It takes a PAC file from user and determine
> > proxy using that file.
>
> But to a PAC-user, both libproxy and pacparser would serve the exact same
> purpose (and in fact I would even assume that libproxy uses pacparser) and
> that is to parse a PAC to figure out the proxy to use for a given url.
>
> I don't understand what purpose pacparser would have in libcurl. Why can't
> applications that need to parse PAC files simply use pacparser (or libproxy)?
>
> I can see how it would be a useful addition to curl though, as an application.

Sure. In the end I just want to see curl using PAC files.

I'll work on the patch to add pacparser to curl if nobody else is
interested in that.

--Manu
Received on 2008-01-25