On Fri, Aug 28, 2009 at 11:02:30AM +1000, Sam Thorogood wrote: > > When a Wave server dials your top-level XMPP server, it will report > (via disco) that it provides a Wave service on > wave.microcomaustralia.com.au. It will then try to resolve this new > address and connect to it (which works since it will have a DNS > fallback) as this is where Wave is actually provided. AFAIK, while you > [and most people] just run Wave as a component of Openfire, there > would be nothing wrong with running a completely different XMPP > server, on a different IP, on wave.* that just responds to Wave > requests.
So are you saying I do or don't need the following entries? _jabber._tcp.wave.microcomaustralia.com.au has SRV record 5 0 5269 chat.microcomaustralia.com.au. _xmpp-server._tcp.wave.microcomaustralia.com.au has SRV record 5 0 5269 chat.microcomaustralia.com.au. _xmpp-client._tcp.wave.microcomaustralia.com.au has SRV record 5 0 5222 chat.microcomaustralia.com.au. My assumption previously was that these are the format of _jabber._tcp.$domain _xmpp-server._tcp.$domain _xmpp-client._tcp.$domain where domain is microcomaustralia.com.au, and are used for looking up the server name if the server name has not been configured and only the domain name is given. They are not used if you give the client the FQDN of the server. As such, my assumption would be that when wave.microcomaustralia.com.au is given, that is the fully qualified name of the name, not the domain, and as such the above DNS entries should not be required. Maybe I should read that draft RFC. Will do so now. -- Brian May <[email protected]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
