libproxy as external dependency

Hi, I'd like to propose libproxy (LGPL 2.1+; http://code.google.com/p/libproxy/) as a blessed external dependency for GNOME 2.26. libproxy is currently used by vlc and neon and libsoup and webkit are considering adopting it. libproxy is a library for handling all aspects of proxy configurat

Re: libproxy as external dependency

Nathaniel McCallum wrote: > I'd like to propose libproxy (LGPL 2.1+; > http://code.google.com/p/libproxy/) as a blessed external dependency for > GNOME 2.26. libproxy is currently used by vlc and neon and libsoup and > webkit are considering adopting it. You need a comma somewhere... Since I know

Re: libproxy as external dependency

Dan Winship wrote: Nathaniel McCallum wrote: I'd like to propose libproxy (LGPL 2.1+; http://code.google.com/p/libproxy/) as a blessed external dependency for GNOME 2.26. libproxy is currently used by vlc and neon and libsoup and webkit are considering adopting it. You need a comma so

Re: libproxy as external dependency

Dan Winship wrote: Nathaniel McCallum wrote: I'd like to propose libproxy (LGPL 2.1+; http://code.google.com/p/libproxy/) as a blessed external dependency for GNOME 2.26. libproxy is currently used by vlc and neon and libsoup and webkit are considering adopting it. You need a comma so

Re: libproxy as external dependency

pros: - current proxy handling in GNOME is a huge mess, we're all lucky we can live without proxies - the API looks extremely sane - there is nothing else that does proxying - Dan (who is going to be the main - or only? - user of it) likes it - active maintainers - no bugs cons: - I'm (luckily) no

Re: libproxy as external dependency

On Tue, 2008-10-21 at 10:30 -0400, Nathaniel McCallum wrote: > I'd like to propose libproxy (LGPL 2.1+; > http://code.google.com/p/libproxy/) as a blessed external dependency for > GNOME 2.26. libproxy is currently used by vlc and neon and libsoup and > webkit are considering adopting it. I'd

Re: libproxy as external dependency

Ross Burton wrote: On Tue, 2008-10-21 at 10:30 -0400, Nathaniel McCallum wrote: I'd like to propose libproxy (LGPL 2.1+; http://code.google.com/p/libproxy/) as a blessed external dependency for GNOME 2.26. libproxy is currently used by vlc and neon and libsoup and webkit are considering ad

Re: libproxy as external dependency

On Thu, 2008-10-23 at 17:35 +, Benjamin Otte wrote: > pros: > - current proxy handling in GNOME is a huge mess, we're all lucky we can live > without proxies > - the API looks extremely sane > - there is nothing else that does proxying > - Dan (who is going to be the main - or only? - user of i

Re: libproxy as external dependency

On Fri, 2008-10-24 at 11:21 +0200, Xavier Bestel wrote: > On Thu, 2008-10-23 at 17:35 +, Benjamin Otte wrote: > > pros: > > - current proxy handling in GNOME is a huge mess, we're all lucky we can > > live > > without proxies > > - the API looks extremely sane > > - there is nothing else that

Re: libproxy as external dependency

2008-10-24 klockan 11:40 skrev Emmanuele Bassi: > but humour me: where would you put this functionality? and saying > libgnome or gtk+ is not going to cut it. libsoup perhaps? — Wouter -- :wq mail [EMAIL PROTECTED]

Re: libproxy as external dependency

2008/10/24 Xavier Bestel <[EMAIL PROTECTED]>: > - yet another library, slowing applications startup. Actually, I've been thinking about this problem lately. Why don't people use dlopen() more often? If you use a library in your app which is not intrinsically essential to it (like gtk+ is) why are

Re: libproxy as external dependency

On Fri, 2008-10-24 at 12:04 +0200, Wouter Bolsterlee wrote: > 2008-10-24 klockan 11:40 skrev Emmanuele Bassi: > > but humour me: where would you put this functionality? and saying > > libgnome or gtk+ is not going to cut it. > > libsoup perhaps? er... http://mail.gnome.org/archives/desktop-devel

Re: libproxy as external dependency

On Fri, 2008-10-24 at 11:09 +0100, Rui Tiago Cação Matos wrote: > In this specific library case, since the API is so simple and you > don't know you need it until you somehow check your app's settings > it's a no-brainer really. You could lazy-load the library when you need to access a URL, but th

Re: libproxy as external dependency

On Fri, 2008-10-24 at 11:09 +0100, Rui Tiago Cação Matos wrote: > 2008/10/24 Xavier Bestel <[EMAIL PROTECTED]>: > > - yet another library, slowing applications startup. > > Actually, I've been thinking about this problem lately. Why don't > people use dlopen() more often? If you use a library in y

Re: libproxy as external dependency

2008/10/24 Ross Burton <[EMAIL PROTECTED]> > On Fri, 2008-10-24 at 11:09 +0100, Rui Tiago Cação Matos wrote: > > In this specific library case, since the API is so simple and you > > don't know you need it until you somehow check your app's settings > > it's a no-brainer really. > > You could lazy

Re: libproxy as external dependency

Ali Sabil wrote: 2008/10/24 Ross Burton <[EMAIL PROTECTED] > On Fri, 2008-10-24 at 11:09 +0100, Rui Tiago Cação Matos wrote: > In this specific library case, since the API is so simple and you > don't know you need it until you somehow check your app's set

Re: libproxy as external dependency

On Fri, Oct 24, 2008 at 11:40 AM, Emmanuele Bassi <[EMAIL PROTECTED]> wrote: > On Fri, 2008-10-24 at 11:21 +0200, Xavier Bestel wrote: >> On Thu, 2008-10-23 at 17:35 +, Benjamin Otte wrote: >> > pros: >> > - current proxy handling in GNOME is a huge mess, we're all lucky we can >> > live >> >

Re: libproxy as external dependency

On Sat, Oct 25, 2008 at 7:38 PM, Nathaniel McCallum <[EMAIL PROTECTED]> wrote: > Ali Sabil wrote: >> >> >> 2008/10/24 Ross Burton <[EMAIL PROTECTED] > >> >>On Fri, 2008-10-24 at 11:09 +0100, Rui Tiago Cação Matos wrote: >>> In this specific library case, since the

Re: libproxy as external dependency

Felipe Contreras wrote: > There's also: > 4. Do the actual proxified communication > > Who is supposed to add the SOCKS 4/5 headers and HTTP proxy stuff? I > don't think libsoup (an HTTP library) is supposed to do that, since > other protocols will need to do the same (IRC, FTP, etc). SOCKS will

Re: libproxy as external dependency

Le mardi 21 octobre 2008, à 10:30 -0400, Nathaniel McCallum a écrit : > Hi, > > I'd like to propose libproxy (LGPL 2.1+; > http://code.google.com/p/libproxy/) as a blessed external dependency for > GNOME 2.26. libproxy is currently used by vlc and neon and libsoup and > webkit are considerin

Re: libproxy as external dependency

Vincent Untz wrote: Le mardi 21 octobre 2008, à 10:30 -0400, Nathaniel McCallum a écrit : Hi, I'd like to propose libproxy (LGPL 2.1+; http://code.google.com/p/libproxy/) as a blessed external dependency for GNOME 2.26. libproxy is currently used by vlc and neon and libsoup and webkit

Re: libproxy as external dependency

Le jeudi 06 novembre 2008, à 07:59 -0500, Nathaniel McCallum a écrit : > Vincent Untz wrote: >> Le mardi 21 octobre 2008, à 10:30 -0400, Nathaniel McCallum a écrit : >> >>> Hi, >>> >>> I'd like to propose libproxy (LGPL 2.1+; >>> http://code.google.com/p/libproxy/) as a blessed external depen

Re: libproxy as external dependency

Le jeudi 06 novembre 2008, à 14:32 +0100, Patryk Zawadzki a écrit : > On Thu, Nov 6, 2008 at 2:23 PM, Vincent Untz <[EMAIL PROTECTED]> wrote: > > What if the connection works in both cases, but the results are > > different? I would guess it's up to the application to know if the > > connection sho

Re: libproxy as external dependency

Le mardi 21 octobre 2008, à 10:30 -0400, Nathaniel McCallum a écrit : > Hi, > > I'd like to propose libproxy (LGPL 2.1+; > http://code.google.com/p/libproxy/) as a blessed external dependency for > GNOME 2.26. libproxy is currently used by vlc and neon and libsoup and > webkit are considerin

Re: libproxy as external dependency

On Thu, Nov 6, 2008 at 2:23 PM, Vincent Untz <[EMAIL PROTECTED]> wrote: > What if the connection works in both cases, but the results are > different? I would guess it's up to the application to know if the > connection should be restarted. > > An example for this (although this is a short-life con

Re: libproxy as external dependency

On Thu, 2008-11-06 at 15:01 +0100, Vincent Untz wrote: > Le mardi 21 octobre 2008, à 10:30 -0400, Nathaniel McCallum a écrit : > > Hi, > > > > I'd like to propose libproxy (LGPL 2.1+; > > http://code.google.com/p/libproxy/) as a blessed external dependency for > > GNOME 2.26. libproxy is curre

Re: libproxy as external dependency

On Thu, Nov 06, 2008 at 03:01:01PM +0100, Vincent Untz wrote: > Le mardi 21 octobre 2008, à 10:30 -0400, Nathaniel McCallum a écrit : > > I'd like to propose libproxy (LGPL 2.1+; > > http://code.google.com/p/libproxy/) as a blessed external dependency for > > GNOME 2.26. libproxy is currently

Re: libproxy as external dependency

Michael Banck wrote: > FYI, a member of the Debian security team raised concerns: > > "WPAD is a broken protocol with security issues inherent to the DNS > devolution mechanism (which is also performed by libproxy). Please > don't add implementations to the Debian archive." > > http://lists.debi

Re: libproxy as external dependency

On Thu, Dec 18, 2008 at 11:25 AM, Dan Winship wrote: > Michael Banck wrote: > > FYI, a member of the Debian security team raised concerns: > > > > "WPAD is a broken protocol with security issues inherent to the DNS > > devolution mechanism (which is also performed by libproxy). Please > > don't

Re: libproxy as external dependency

On Thu, 2008-11-06 at 15:01 +0100, Vincent Untz wrote: > So I guess we can accept it, unless someone else raises another issue? I think we have to accept it. It's a stable library that solves a real problem written by people who are approachable and know what they are doing. +1 from me. Richard.