Takigama wrote: > see the way i thought it worked was that server-to-server is always > via "server.domain.com", then client-to-server is via > "wave.Server.domain.com". Which is what your saying pretty much - i.e. > all comms from server to server is via xmpp. > > For eg, i've not played with jabber/openfire/xmpp too much, but i > always thought if you wanted to "conference" with someone across chat > you addressed them as [email protected] - or maybe > i've missread that part > > I've removed all traces of wave.server.domain.com from my config and > it appears to be all working again. > > On Aug 18, 3:35 am, "[email protected]" > okay from what I've worked out this is the way Server->Server communication works:
First server communicates with the XMPP server at the root domain (in my case that's wave.collaborynth.com.au). The second server then returns a list of the available components as subdomains of the root domain (again in my case, that means the wave component gets returned as wave.wave.collaborynth.com.au) Hence you need the root domain for the initial communication and the component sub domain for component to component communication. The client->server stuff doesn't require DNS setup. You can very easily use a raw IP Address (which is what I do, my client is on my laptop and my server is on a vm). Hope that clears things up. -- James Purser Collaborynth http://collaborynth.com.au Mob: +61 406 576 553 Skype: purserj1977 twitter: www.twitter.com/purserj GTalk: [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 -~----------~----~----~----~------~----~------~--~---
