[jdev] How to handle AIM/external protocol users with "@" in buddyname

[Paul Clegg]

Thanks Matt, this is just what I was looking for. We'll follow up with 
Daniel from PyAim-t (if he doesn't see this on jdev) and we'll prepare a 
patch for aim-t.

-Paul

On 4/28/05, Matt Tucker <matt at jivesoftware.com> wrote:
> 
> Paul,
> 
> Please check out the JID Escaping JEP:
> http://www.jabber.org/jeps/jep-0106.html. The transport you're using
> might need to be updated to support this, but it seems like the right
> approach. There's been a lot of discussion about this JEP on the
> standards-jib mailing list recently.
> 
> Regards,
> Matt
> 
> > -----Original Message-----
> > From: jdev-bounces at jabber.org
> > [mailto:jdev-bounces at jabber.org] On Behalf Of Paul Clegg
> > Sent: Thursday, April 28, 2005 9:25 AM
> > To: jdev at jabber.org
> > Subject: [jdev] How to handle AIM/external protocol users
> > with "@" in buddyname
> >
> > We recently discovered a class of AIM users who have an "@"
> > symbol in their buddy name (e.g. buddyname at somecompany.com).
> > Neither aim-t or pyaim-t handle this case (the buddy is
> > translated to the jid buddyname at somecompany.com@
> > transport.server.com <http://transport.server.com> <
> http://transport.server.com>, which is
> > clearly not a legal jid).
> >
> > Can anyone recommend the correct way to resolve xmpp-illegal
> > characters encountered in external protocols at the transport
> > level, so that the contact can be properly assigned a jid,
> > messaged, stored in the roster, etc.?
> >
> > I imagine that the MSN-t folks have dealt with this issue
> > already and may have some suggestions for us.
> >
> > Thanks,
> >
> > Paul
> > _______________________________________________
> > jdev mailing list
> > jdev at jabber.org
> > http://mail.jabber.org/mailman/listinfo/jdev
> >
>