Jonathan Schleifer wrote:
Am 20.08.2008 um 01:01 schrieb Peter Saint-Andre:<message from='[EMAIL PROTECTED]/desktop' to='[EMAIL PROTECTED]'> <x xmlns='http://jabber.org/protocol/muc#user'> <invite to='[EMAIL PROTECTED]' id='some-long-id-here'/> ^^^^^^^^^^^^^^^^^^^^^^ </x> </message>How about this instead? <message from='[EMAIL PROTECTED]/desktop' to='[EMAIL PROTECTED]'> <x xmlns='http://jabber.org/protocol/muc#user'> <invite to='[EMAIL PROTECTED]'> <id>some_id (doesn't even need to be long)</id> </invite> </x> </message>
Element, attribute, whatever.
Are you sure current implementations will not route that?
No, I have not yet tested that. But it's easy enough to do.
For the clients, it doesn't matter if they ignore it, because that means they only support mediated invitations and not direct invitations. Only new clients will implement directed invitiations, and if we make the ID a part of that, they will implement it.
Right. /psa
smime.p7s
Description: S/MIME Cryptographic Signature
