[Telepathy] Stage of proxy support
nicolas.dufresne at collabora.co.uk
Mon May 3 14:53:39 PDT 2010
Le lundi 03 mai 2010 à 23:01 +0200, Gendre Sébastien a écrit :
> I have a question: What stage is the proxy support in telepathy ?
> Someone already working on it?
I'm currently doing some work that will bring proxy support to Telepathy
Gabble. Has Gabble uses (through Wocky) GSocketConnection from Glib, we
decided that the best place to have proxy support is inside GLib.
The Glib work is mostly done now, I'm doing some cleanup and
documentation before the review process starts. If you want to have a
look, the code can be found at:
> If I can help, don't hesitate to ask me, but not before mid-June. ^_^
Aside this, there is still a lot of work and decisions to make. For
other component, one will have to decide between porting to GNIO or
reimplementing it. So far I have not discussed this with any of the
maintainers. The GNIO way may take more time, but will lead to a well
tested and unified proxy support.
On Glib part, I still need to implement SOCKSv4a, SOCKSv4 and HTTP
Connect. Those implements GProxy interface and register to "gio-proxy"
For LibProxy, an internal API change has been planned to allow more
flexible configuration. One of my goal is to allow trying HTTP Connect
(usually the HTTPS proxy configuration) for any protocols with a direct
fallback (since using HTTP connect is an abused that may get block for
non-standard ports like 443). For more information, just connect to
Butterfly (Papyon) and Haze (libpurple) already have a partial proxy
support but it does not get configured. A libproxy integration is
required here. Specially for Haze, it may be simpler to wait until GLib
patches goes upstream (hopefully 2.26).
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the telepathy