On Mon Oct 12 21:11:00 2009, Yann Leboulanger wrote:
Does this mean the room is not joinable (it's what XEP86 says)?
Yes.
Or does this mean maximum number of participant has been reached
(it's
ehat XEP45 says)?
Maybe that's the reason it's not joinable.
I know XEP 86 is deprecated, but at least ejabberd still implement
that,
and it returns the exact same answer in both case. I'm not sure
which
XEP is wrong, if any ...
Or, as Joe says, it might mean the host is unreachable.
Or - maybe - it means the moon is in the seventh phase.
Is anyone interested in defining some sensible error elements for
XEP-0045?
So this might become:
<presence from='r...@server/nick' to='jid' type='error' id='816'>
<error type='cancel'>
<limit-exceeded xmlns='urn:xmpp:muc:errors:0'>
<service-unavailable xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
</error>
</presence>
I know this won't solve your immediate problem, but it'd be nice to
tidy up MUC a bit, and remove some of the warts it has.
(I'm also up for considering changing <status code='182'/> to
something meangingful, too - a lot of those are ignored by clients
right now anyway.)
Dave.
--
Dave Cridland - mailto:[email protected] - xmpp:[email protected]
- acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
- http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
