Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
XEP-0156 (Discovering Alternative XMPP Connection Methods)
See original GitHub issueIf 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. </bountysource-plugin>
Issue Analytics
- State:
- Created 10 years ago
- Reactions:3
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Party!
XEP-0156 (Discovering Alternative XMPP Connection Methods) also specifies a pure HTTP discovery method.