I an running a web server at danopia.net and I run my wave server at wave.danopia.net, which CNAMEs to home.danopia.net, which CNAMEs to danopia.no-ip.org. I don't think it's necesary to use wave. but it's recommended. You probably can use whatever, but XMPP requires each component to have a subdomain, and Wave uses wave. for this. My custom provider works with *any* JID, as long as it is labeled "google-wave". I personally run my custom provider at newwave.danopia.net. and the only sideaffect is some servers ignoring me completely because I don't have _xmpp-server._tcp.newwave.danopia.net.
On Oct 26, 5:22 pm, fahadsadah <[email protected]> wrote: > Greetings, wave-protocol. > > For the purposes of example, I will invent a fictious corporation, > Corp, at corp.com. > corp.com is the web server for Corp > mail.corp.com is the email server (incoming SMTP) > > In email, I can set an MX record for corp.com, pointing to > mail.corp.com, so that email sent to addresses at corp.com will reach > mail.corp.com. > However, I can name mail.corp.com whatever I like, as long as the MX > record is still correct. If I want to use turnips.corp.com, I can. > Also, note that corp.com and mail.corp.com can both resolve to > different addresses - they can be different servers. > > Now, say I want to set up Wave for Corp. According > tohttp://code.google.com/p/wave-protocol/wiki/Federation, I have none of > this flexibility. > Both corp.com and wave.corp.com must resolve to the wave server. This > is not always practical - for example, I was recently attempting to > implement wave for an organisation, and was unable to do so - we need > our root domain to point to our web server. > Also, notice that I can't call the wave subdomain whatever I wish, but > am restricted to wave. This is not so much of a problem, but it would > be nice to have the option to rename, later. > I am also required to add SRV records at _xmpp-server_._tcp.corp.com > and _xmpp-server_._tcp.wave.corp.com, to indicate ports. The > duplication is unnecessary. > > This is inconvenient, overkill, and, often, impossible. > > I propose the following solution: > > We define a new resource record, WX, identical to email's MX record. > We will use the following DNS structure: > corp.com has a WX record to Corp's wave server (in this example, > wave.corp.com) > wave.corp.com has a SRV record of the TCP port that XMPP is listening > on, on wave.corp.com. > > As an alternative to defining a new record, WX, SRV records could be > used. > > I will hack together a patch to implement this in the wave-protocol > example server, either tomorrow, or the day after. > > Many thanks, > Fahad Sadah --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en -~----------~----~----~----~------~----~------~--~---
