Thanks. In fact, I have tried libproxy, but libproxy also call GConf API, so libproxy also can't get the correct proxy info. Seems the runtime environment is changed in libzypp. Any comment?
-Thanks -Qiang -----Original Message----- From: Damien Lespiau [mailto:damien.lesp...@intel.com] Sent: 2010年3月31日 18:34 To: Zhang, Qiang Z Cc: meego-dev@meego.com Subject: Re: [MeeGo-dev] GConf API Usage issue On Wed, 2010-03-31 at 07:51 +0100, Zhang, Qiang Z wrote: > Hello all, Hi, > GConfValue *v = gconf_client_get(client, > "/system/http_proxy/host", &error); Note that poking GConf for proxy configuration is *not* how one should query the proxy information. The way to do it is to go through libproxy[1], which happens to mimic the way firefox has done it in the first place (GConf keys, GNOME plugin in libproxy). For instance, using libproxy will allow you to support proxy auto configuration out the box, something that needs a javascript engine, nothing less... http://en.wikipedia.org/wiki/Proxy_auto-config HTH, -- Damien [1] http://code.google.com/p/libproxy/ _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
