Opened 14 years ago

Closed 13 years ago

#18 closed enhancement (fixed)

clean access to jid in XMPPClient

Reported by: tofu Owned by: ralphm
Priority: normal Milestone:
Component: generic Keywords:


Right now you have to access the jid via the authenticator, I think it would be nice if there was a self.jid to access.

Also, it would be cool to set the resource when the client binds to the xmpp server. For example, gmail changes your resource and it would be nice to know what it is in some cases.

Change History (3)

comment:1 Changed 14 years ago by jack

+1 from me. Also you will need this if SASL anonymous is used to get the bare jid too.

comment:2 Changed 14 years ago by ralphm

Yes, it is quite a hassle to get to the JID right now, so I agree we need to do that better. Maybe we can use a proxied attribute for that, that is implemented as a property that really reads the JID from the authenticator. I'll think about that.

That said, the implementation of the resource binding has always stored the returned JID in the jid attribute of the authenticator. See twisted.words.protocols.jabber.client.BindInitializer.

comment:3 Changed 13 years ago by ralphm

  • Resolution set to fixed
  • Status changed from new to closed

(In [190]) Add a jid attribute to XMPPClient that is updated with the current JID.

Author: ralphm. Fixes #18.

Note: See TracTickets for help on using tickets.