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.

On 7/3/07, Chris Carlin <[EMAIL PROTECTED]> wrote:

Nat Burke wrote:
> I'm using pyaimt 0.8a.  Also just to note, normal message
> communication is possible.  Does the pyAIMt automatically respond to
> the subscribe presence?  Is the format different than a standard
> subscribe presence?  Thanks for at least looking at this one Chris.
Actually, come to think of it, no: when you sign on to a transport the
transport can show your status to anyone else. Consider that AIM doesn't
really have the concept of subscribing (block lists are a bit
different). Whenever you sign on through the transport, anyone who could
normally see the AIM user sign on will get the message that the user has
signed on.

With regard to transports, subscriptions are sort of a wrapper around
the non-native contact. You subscribe to the presence of
[EMAIL PROTECTED], and then the transport at aim.whatever.com gets to
figure out what that means. It may mean that some subscription request
is passed along for approval, but it may also mean (and does here)
nothing except that the transport will provide the notification. Going
the other way it means that subscriptions are assumed to be approved
already.

That's long winded and possibly completely wrong, so take it as you will
:) The summary is that subscription requests are generated only when
absoutely needed to complete the illusion that someone is using Jabber.

~Chris
_______________________________________________
py-transports mailing list
py-transports@blathersource.org
http://lists.modevia.com/cgi-bin/mailman/listinfo/py-transports

_______________________________________________
py-transports mailing list
py-transports@blathersource.org
http://lists.modevia.com/cgi-bin/mailman/listinfo/py-transports

Reply via email to