Difference between revisions of "XEP-Remarks/XEP-0045: Multi-User Chat"

Jump to navigation Jump to search
m
no edit summary
(→‎Why do I need to host my MUC component on subdomain.example.org?: Mention disco#items on room to get occupant list)
m
 
Line 66: Line 66:
http://mail.jabber.org/pipermail/standards/2015-May/029819.html
http://mail.jabber.org/pipermail/standards/2015-May/029819.html


= Why do I need to host my MUC component on subdomain.example.org? =
= Why do I need to host my MUC component on subdomain.domain.tld? =


You don't. You don't even need to host it on "example.org", you can host it on any bare JID you want (without a resource, with or without a node).
You don't. You don't even need to host it on "domain.tld", you can host it on any bare JID you want (without a resource, with or without a node).
Not all clients will be able to join, because this isn't how it's always been done but technically nothing prevents it.
Not all clients will be able to join, because this isn't how it's always been done but technically nothing prevents it.


You also can have a room directly on subdomain.example.org, or example.org.
You also can have a room directly on subdomain.domain.tld, or domain.tld.


Clients will generally expect to be able to create rooms on the address that is given to them in disco#items on the host (the "MUC component").
Clients will generally expect to be able to create rooms on the address that is given to them in disco#items on the host (the "MUC component").
217

edits

Navigation menu