This looks ugly and unnecessary to me.

On Wed, 20 Aug 2008 16:01:54 +0200
Jonathan Schleifer <[EMAIL PROTECTED]> 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>
> 
> Are you sure current implementations will not route that?
> 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.
> 
> --
> Jonathan


-- 

Web: http://www.pavlix.net/
Jabber & Mail: pavlix(at)pavlix.net
OpenID: pavlix.net

Reply via email to