On Wed, Mar 30, 2011 at 11:34 PM, Matthew Wild <[email protected]> wrote: >> As a web client user I would prefer the client to use the BOSH service >> available on my XMPP server. >> > > Unfortunately the above XEP is of limited use in a web client (that > said, it could be made to work in a smart web client with some > server-side code). The Javascript environment in a web browser does > not have access to generic DNS lookups, and in most deployed browsers > it can't even make a request to any site other than the one the script > was downloaded from. > >> As a web client developer/administrator I would prefer users being able to >> use their own BOSH service because I don't want mine being overloaded. >> > > One way to implement this would be with some server-side code that > looks in DNS on behalf of the web client for the user's server's BOSH > URL. If one exists, it hands that to the web client. The web client > then tries to use this URL - it may fail if the user doesn't have a > browser with cross-domain support, or if the remote server also > doesn't support cross-domain requests. If it fails it could fall back > to your BOSH service.
http://dig.jsondns.org/ https://github.com/jpf/jsondns
