[ANN] libproxy 0.2

[Alex Panait]

Sorry about the long delay.

Providing a proxy server connection is outside the current scope of
libproxy. However, libproxy does have the ability to autodetect proxy
settings if none are provided, via WPAD.

libproxy does not have any special treatment for different proxy
types. So for a SOCKS4 proxy libproxy will just end up returning a URL
with a different scheme.

I hope that addresses your questions. Let me know if I can help with
anything else! Also, Happy (belated) New Year!


Alex

On 12/22/07, Mark Doliner <mark at kingant.net> wrote:
> On Fri, 21 Dec 2007 12:39:57 -0600, Felipe Contreras wrote
> > On Dec 21, 2007 11:23 AM, Alex Panait <kippled at gmail.com> wrote:
> > > I would like to announce the release of version 0.2 of libproxy, an
> > > open-source library that provides functions to manage proxy
> > > configurations uniformly across applications and user sessions.
> > > libproxy has a stable API and modules to read configuration from
> > > GNOME, KDE, a file, or an environment variable (for compatibility with
> > > existing implementations). In addition, libproxy automatically adjusts
> > > for changing network topology via integration with NetworkManager and
> > > is able to autodetect proxy settings through WPAD and PAC compliance.
> > >
> > > Through these features, an application that links to libproxy will not
> > > have to worry about proxy configuration or even a change of networks:
> > > libproxy will automatically provide the correct proxy to use.
> > >
> > > Please have a look at http://libproxy.googlecode.com for more info. A
> > > bug requesting libproxy adoption has also been filed:
> > > http://developer.pidgin.im/ticket/4459.
> >
> > Great news!
> >
> > This is something that's definitely needed, everyone re-implementing
> > their own proxy code is just inefficient and stupid.
> > I tried to start something like this but I never had enough time.
>
> Hmm, it doesn't seem like this library actually implements code for connecting
> through proxy servers... it looks like it just grabs proxy settings from
> various places and determines which proxy server should be used.  Alex, is
> that correct?
>
> Also, I took a peak at the API a bit and I don't see a way for libproxy to
> specify the proxy type (HTTP verse SOCKS4 verse SOCKS5).  Is it just always
> assumed that the proxy is an HTTP proxy?
>
> -Mark
>