Good day, I'm running into a bit of strange edge case, with the pymsnt (v 0.11.2) and ejabberd (v 1.1.3-4) on linux (both fedora core 6 and RHE4). In doing some testing of the two of these, I've run into the following use case (100% reproducable):
1/ jabber user a registers with pymsnt as msn user x 2/ jabber user a, connected as msn user x has a from subscription to msn user y, reported by pymsnt from roster subsync packet. The jabber roster is synchronised to match this. 3/ a subscribes to msn user y (succeeds, now 2-way subscription) 4/ within the same pymsnt session, a sends an unsubscribe packet to msn user y (at this point, The pymsnt session dies for the user, without any info in the logs as to why (log level 4). 5/ jabber user a creates a session with pymsnt, as msn user x, and gets presence info for msn user y. After this point, a can perform any number of adds/removals of y without problem. This is the only combination of subscription statuses and requests for which I've seen this behaviour, but as mentioned, it is 100% reproducable. I've seen this on multiple systems (using same versions of pymsnt and ejabberd). Both twisted 1.x and 2.x libraries exhibit similar behaviour. I've not tested to see if 4/ above happens with any other jabber server (that's the next step here), but figured it would be worthwhile in the meantime to see if this is a known issue, either with pymsnt directory, or an interoprability issue between it an ejabberd. Cheers, Mark. _______________________________________________ py-transports mailing list py-transports@blathersource.org http://lists.modevia.com/cgi-bin/mailman/listinfo/py-transports
