<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.26.3"> </HEAD> <BODY> Hi Sébastien, Le lundi 03 mai 2010 à 23:01 +0200, Gendre Sébastien a écrit : <BLOCKQUOTE TYPE=CITE> <PRE> I have a question: What stage is the proxy support in telepathy ? Someone already working on it? </PRE> </BLOCKQUOTE> 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: <A HREF="http://git.collabora.co.uk/?p=user/nicolas/glib.git;a=shortlog;h=refs/heads/proxy">http://git.collabora.co.uk/?p=user/nicolas/glib.git;a=shortlog;h=refs/heads/proxy</A> <BLOCKQUOTE TYPE=CITE> <PRE> If I can help, don't hesitate to ask me, but not before mid-June. ^_^ </PRE> </BLOCKQUOTE> 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" extensions point. 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 freenode #libproxy. 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). Best regards, Nicolas Dufresne </BODY> </HTML>