[Standards] XEP-0045: direct invitations

Michal 'vorner' Vaner vorner at ucw.cz
Thu Jul 19 21:43:54 UTC 2007


Hello,

On Thu, Jul 19, 2007 at 03:34:25PM -0600, Peter Saint-Andre wrote:
> Michal 'vorner' Vaner wrote:
> > Hello
> > 
> > On Thu, Jul 19, 2007 at 02:27:51PM -0600, Peter Saint-Andre wrote:
> >> Currently it is not possible to send room invitations directly from one
> >> person to another. That is, the invitation must go through the room. See:
> >>
> >> http://www.xmpp.org/extensions/xep-0045.html#invite
> >>
> >> This can cause problems with deployments that use privacy lists to block
> >> communications from entities that are not in your roster.
> >>
> >> In order to solve this issue, we need to modify the <invite/> element in
> >> XEP-0045. Currently the flow is like this:
> > 
> > Hm, just a question - how do you handle the tricks like adding the user
> > to member list, adding a password to the invitation (that could have
> > change since the occupant entered, so he does not know the new one, or
> > his client does not) or room that does not allow you to send invites?
> 
> You don't.

Wouldn't it be nice to be able to do something about it? For example
send an iq to the MUC server to prepare the stanza for you and you just
sent it out? Like ask it for an advice (optional)?

<iq to='muc at room' type='get'>
  <advice xmlns='…'>
    <invite 
      …
    </invite>
  </advice>
</iq>

<iq from='muc at room' type='result'>
  <advice xmlns='…'>
    <invite 
      …
    </invite>
  </advice>
</iq>

You do not send client from sending an invitation, but as you said, you
can say it to the other person the social way. This allows the other
tricks at last.

-- 
This message has optimized support for formating.
Please choose green font and black background so it looks like it should.

Michal 'vorner' Vaner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/standards/attachments/20070719/ef92c501/attachment.sig>


More information about the Standards mailing list