it is possible to have a disconnectHandler colled during the con.connect() function if jabber server is brocken.

This commit is contained in:
Yann Leboulanger 2004-05-25 01:16:02 +00:00
parent 3a91cda882
commit b5cf353af9
1 changed files with 1 additions and 1 deletions

View File

@ -204,6 +204,7 @@ class GajimCore:
connection=common.xmlstream.TCP, port=5222, proxy = proxy)
#debug = [common.jabber.DBG_ALWAYS], log = sys.stderr, \
#connection=common.xmlstream.TCP_SSL, port=5223, proxy = proxy)
con.setDisconnectHandler(self.disconnectedCB)
try:
con.connect()
except IOError, e:
@ -224,7 +225,6 @@ class GajimCore:
con.registerHandler('message', self.messageCB)
con.registerHandler('presence', self.presenceCB)
con.registerHandler('iq',self.vCardCB,'result')#common.jabber.NS_VCARD)
con.setDisconnectHandler(self.disconnectedCB)
#BUG in jabberpy library : if hostname is wrong : "boucle"
if con.auth(name, password, ressource):
self.connexions[con] = account