Converse.js: XEP-0156 (Discovering Alternative XMPP Connection Methods)

[koehn]

If I have properly set up a BOSH server and configured my DNS to serve up a URL per XEP-0156 (e.g., koehn.com), there's no need to use a third-party connection manager. The system could check the DNS for a TXT record at the XMPP host with text starting with _xmpp-client-xbosh and use that as the connection manager.

Trouble is I'm not sure how you do a TXT DNS resolution from the browser; you certainly could have a server-side component to do the discovery though, you'd just have to have a standard API to send the user's JID and get back the connection manager to use. The server-side component could get the domain of the JID, check the XEP-0156 DNS entries, and return either a default connection manager or the one used by the domain.

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[koehn]

Helluva nice library, by the way.

[jcbrand]

Thanks. Would be nice if this could be done in the browser.

Here's an example of DNS in client-side JS: http://www.fileformat.info/tool/rest/dns-json.htm (not open source it seems).

[devurandom]

XEP-0156 (Discovering Alternative XMPP Connection Methods) also specifies a pure HTTP discovery method.

[Neustradamus]

Any news about this ticket?
5 years old already!

[wiktor-k]

For the record XEP-0156 now recommends using CORS so that the host-meta file is discoverable from other domains and the Compliance Tester has been adjusted to check for CORS headers.

[poVoq]

https://github.com/jsxc/xmpp-connection-discovery-node

[poVoq]

Party!