Am So., 4. Okt. 2020 um 17:12 Uhr schrieb Georg Lukas <[email protected]>:
> > 2. Which of the above elements MUST a room on the domain have? > the identity conference/text and the feature. because conference/text only points to a chat text service, not specifically a MUC, that's what the feature is for. At least that's what i get from https://xmpp.org/registrar/disco-categories.html#conference > > 3. If the room in question does not exist, but would be auto-created on > join, how can this be discovered by a client? > A disco info request to the address will yield item-not-found or some similar error > > 4. Which of the above XML elements should a client use to determine > whether a bare JID is a room? ...whether a domain JID is a MUC service? > service and room need an identity conference/text and the feature https://xmpp.org/extensions/xep-0045.html#registrar-discocat https://xmpp.org/extensions/xep-0045.html#registrar-features > 5. What is the right order of events for a client trying to determine > whether to add a JID to the roster or to join it as a room? > > - Send disco#info to the bare JID > - success: decided according to #4 above > - join room / add contact > - item-not-found: send disco#info to domain JID? Maybe? > - success: decide according to #4 > - join room / add contact > - failure: show an error > > This is two or three round-trips, and not very elegant. But the shortcut > of sending a disco#info to the domain has led to funny errors in the > past, and sending disco#info to the bare JID is insufficient if it is a > room that doesn't exist but would be created on join. > I'm not following, do you believe disco info to a bare account jid will yield item-not-found if it does not exist? That's not the case if you get back item-not-found you can assume you are talking to a muc service so i don't see why you need a disco to the domain jid Regards Philipp
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
