Gajim-devel July 2008

gajim-devel@gajim.org

4 participants
2 discussions

Gajim-svn and problem with SOCKS5 proxy
by Marcin Zajączkowski 03 Jul '08

03 Jul '08

Hello, I'm unable to use SOCKS5 proxy (tested with privoxy & tor and Gajim-svn - 20080604 night build). Every time I try to connect I see on my console (gajim.py -v): DEBUG: CONNECTproxy start Plugging <common.xmpp.transports_nb.NBSOCKS5PROXYsocket instance at 0x98015cc> into <common.xmpp.client_nb.NonBlockingClient instance at 0x904e08c> DEBUG: CONNECTproxy start Proxy server contacted, performing authentification DEBUG: CONNECTproxy sent and nothing more happens. I tried with using HTTP_PROXY environment variable and manual proxy definition as well. I haven't find any similar tickets in trac. Maybe you know what can be wrong? Is it possible to increase a logging level to see more details about that? Regards Marcin

2 8

blocking getaddrinfo
by Tomas Karasek 01 Jul '08

01 Jul '08

Hi, I'm trying to get rid of the GUI-blocking timeout that occurs on getaddrinfo() during connecting to XMPP server when network is down. In such case, getaddrinfo blocks for quite a long time and roster window doesn't respond. It happens on connect after executing Gajim, and also when Gajim disconnects due to a network failiure and then tries to reconnect (and network is still down). I was talking about that with Asterix and because we didn't find any AAAA-capable asynchronous python dns library, we came up with following: Because SRV requests are done asynchronously via nslookup in pipe polled in IdleQueue (src/common/nslookup.py), it's possible to detect that DNS server is not available from result of asynchronous SRV request. And - if we know that DNS SRV request failed, then don't do the getaddrinfo call. But now I found out that there is a short blocking timeout when closing pipe with running nslookup - on self.pipe.close(), so this is not a solution for GUI blocking on connect. I already tried putting getaddrinfo to separate thread, but it just didn't work for me - the thread was waiting even after a successful gai call... As for dns libraries - adns can't do AAAA requests, pydns and dnspython can't operate asynchronously. What I'm looking for is either - some elegant way how to do both A and AAAA requests asynchronously (like nonblocking getaddrinfo) which would be a nice solution or - nonblocking detect that network is down which would allow to avoid needless call of getaddrinfo (temporary solution until some suitable library appears) Do you have any ideas/suggestions on this? rgds, tomk -- Tomas Karasek jabber: tom.to.the.k at jabber.cz GSoC blog: http://tomk-soc08.blogspot.com/

5 8

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Gajim-devel July 2008