Note that you can use any component JID, not just wave.domainname.com, so long as your XMPP server supports disco. If for what ever reason you don't support disco, you have to use wave.domainname.com
On Tue, Nov 3, 2009 at 16:31, Devyn Cairns <[email protected]> wrote: > Maybe "wavesandbox.com" is an alias for "wave.wavesandbox.com"? > Anyhow, wave.* is not defined anywhere in the spec. So no, you do have to > use @wave.xmppnews.com, otherwise it will go to your normal xmpp account. > > On Mon, Nov 2, 2009 at 12:54 PM, bear <[email protected]> wrote: >> >> Have to admit this is some cool stuff ;) >> >> I have my wave server setup as a component wave.xmppnews.com to my >> xmppnews.com server - my JID is [email protected]. >> >> In order for my dev sandbox account to send to the federated server I >> had to use [email protected] as the contact id instead of the JID >> - is this expected? I'm asking because my sandbox account is >> [email protected] but I see in the data that the wave server >> identifies itself as @wave.wavesandbox.com >> >> Also, I can type in the sandbox client and see the updates on the >> command line client window, but nothing I type in the command line >> client gets sent to the sandbox account. >> >> More details later as I figure out how to decode the log streams and >> see if there are any error messages :) >> >> but I did get data flowing sandbox -> federated so that's a partial >> win :) >> >> thanks, >> >> > > > > -- > ~devyn > > > > -- Anthony Baxter, [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 -~----------~----~----~----~------~----~------~--~---
