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

Line 65:

http://mail.jabber.org/pipermail/standards/2015-May/029819.html

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

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).

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.

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").

And also they may disco#items it to get a list of rooms hosted on the component. Both of which don't conflict with the same address also being a room.

Maybe a more explicit disco feature should be added to say "You can create rooms off here". Without this, it isn't possible to say whether room creation is actually possible other than trying and reading the error. It would also probably look very awkward for a client to try to create a room off a "component"/"room" hosted at "foo@domain", trying to create "bar@foo@domain" which isn't a valid JID.

= Joining Cisco Jabber Rooms =

@@ Line 65: / Line 65: @@
 http://mail.jabber.org/pipermail/standards/2015-May/029819.html
+= Why do I need to host my MUC component on subdomain.example.org? =
+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).
+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.
+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").
+And also they may disco#items it to get a list of rooms hosted on the component. Both of which don't conflict with the same address also being a room.
+Maybe a more explicit disco feature should be added to say "You can create rooms off here". Without this, it isn't possible to say whether room creation is actually possible other than trying and reading the error.  It would also probably look very awkward for a client to try to create a room off a "component"/"room" hosted at "foo@domain", trying to create "bar@foo@domain" which isn't a valid JID.
 = Joining Cisco Jabber Rooms =

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

Navigation menu

Search