Hi there :)
I have a big problem with PyMSNt... When I try to chat with my friend
through it, I have to send the same msg several times, until it will go
through :|
All the other times I get this in the logs:
> 2006/01/08 14:49 CET [XmlStream,client] INFO :: :: Sending error
response to a message outside of session. :: onMessage ::
<main.PyTransport instance at 0x4075930c> :: {'body': u'some body...',
'el': <tlib.domish.Element object at 0x4076e50c>, 'froj':
<tlib.jabber.jid.JID instance at 0x4076e9cc>, 'self': <main.PyTransport
instance at 0x4075930c>, 'fro': u'[EMAIL PROTECTED]/Psi', 'ulang': None, 'to'
: u'[EMAIL PROTECTED]', 'child': <tlib.domish.Element object at
0x4076ef4c>, 'mtype': u'chat'}
And it sends me a msg that I should first log in to the transport... But
I, of course, AM logged in...
Please help... :)
Cheers,
Saviq
-------------- next part --------------
A non-text attachment was scrubbed...
Name: michal.vcf
Type: text/x-vcard
Size: 210 bytes
Desc: not available
Url :
http://modevia.com/pipermail/py-transports/attachments/20060108/55b41b5d/michal.vcf
From [EMAIL PROTECTED] Mon Jan 9 01:14:31 2006
From: [EMAIL PROTECTED] (Steve Ramage)
Date: Mon Jan 9 01:14:54 2006
Subject: [py-transports] Py*T Connection Test
Message-ID: <[EMAIL PROTECTED]>
Sometimes I notice that PyMSNt thinks its connected but in truth its
not. It might perhaps be a client issue, and its never really a big
thing. However I'm integrating a website with Jabber and thru Jabber &
PyMSNt, with MSN. I know that by sending the transport the message with
end, it will terminate it. Is there something I could send to verify
that I'm still really connected?
Steve R
