Nat Burke wrote: > Thanks for the summary Chris. I have done some more experimentation > and have discovered some new information. It seems like when my > client app is logged in and a new user adds my app bot as a buddy I > see no presence or subscription. However, when I kill the app and > start it again, I get the expected subscribe presence messages and > start to see the presence status of the new user. Have you seen this > behavior before? Can you give me a little push in the right direction > if I end up having to modify the transport to behave more consistently > with the pyMSNt and native Jabber? Again, I appreciate you taking the > time. Would you mind rephrasing that with a little more clarification in terms of what's what? :)
Is your "app bot" the same thing as your "client app", and is it a normal Jabber program logged in through the Jabber server as an end user? Then are you saying that when you log out the client app and log it back in, Jabber then keeps you updated on the status of AIM users who have added the account? Does this always work? The strangest thing here is that I don't believe the AIM protocol has the capability to inform an AIM user that he has been added to a buddy list. The only way to know that another AIM user exists is to receive a message from him, even if it's a "user is typing" message. ~Chris _______________________________________________ py-transports mailing list py-transports@blathersource.org http://lists.modevia.com/cgi-bin/mailman/listinfo/py-transports
