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]" <[email protected]> wrote: > Hi, > > I posted a similar question in the "post details of your federation > server here" thread. > > You use server.domain.com (your xmpp server), not > wave.server.domain.com in run-server.sh > > I'm not sure I understand the whole thing, but communication between > federated wave servers occurs over the xmpp federation protocol. (The > Wave Federation Protocol runs on top of it.) > > When an xmpp disco#items query is run on server.domain.com, it will > find an xep-0114 extension "wave.server.domain.com". (I think a better > JID would be server.domain.com/wave, myself.) The remote xmpp server > then does a dns lookup of wave.server.domain.com and connects to it to > do the federated communications. So it must resolve to the same IP as > server.domain.com so that communications come back to your xmpp > server. > > Hope that helps, > David > > On Aug 15, 10:18 pm, Takigama <[email protected]> wrote: > > > Hi all, > > > mines up and running and its working ok between two machines at home > > (ubuntu 9.04 32bit and fedora 10 64bit - though fedora 10 seems to > > have a few issues). > > > What I am confused about is server naming. So lets say my domain is > > "domain.com". My openfire server thinks its "server.domain.com" and I > > add a subdomain component "wave" which comes up as > > "wave.server.domain.com" (pretty straight forward so far). Where im > > getting confused is how to configure the server and the client. > > > At the moment, my run-server looks like this: > > > CERTIFICATE_DOMAIN_NAME=wave.server.domain.com > > MPP_SERVER_HOSTNAME=server.domain.com > > XMPP_SERVER_IP=server.domain.com > > > Certificates were created with wave.server.domain.com > > > So in the client it looks like this: > > > WAVE_SERVER_DOMAIN_NAME=wave.server.domain.com > > > I have both internal and external dns entries for all of this, but the > > original "run-server" just uses the XMPP_SERVER_HOSTNAME > > (server.domain.com) rather then the sub-domain > > (wave.server.domain.com). I've tried both and not gotten anything > > external as yet, but i've not really tried too hard. Should I appear > > to clients as wave.server.domain.com or server.domain.com? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
