TODO: Move links over to apache infra, XMPP instructions still up to date?Apache infra. Explain server.federation.config.

Introduction

Okay, so now you have WIAB up and running on your laptop. You can successfully login and talk to yourself. Now you're getting the urge to talk to other people on other Wave servers. In order to do this you need to Federate.

...

1. A domain name
2. An ssl certificate from a trusted source (in this case, we use StartSSL) (Recommended, but not necessary whilst you test federation)
3. An XMPP server

Most of the instructions for setting up these things are found in the following child pages:

...

The utility of waves is greatly enhanced if they can be federated in the sense that they are shared between users from different organisations, hosted by different service providers across the Internet. This is accomplished by the Apache Wave federation protocol, a server-to-server network protocol between service providers, supporting low-latency, concurrent updates to conversations ("live typing") and domain authentication.

STOP.

IF YOU ARE JUST TRYING TO SETUP FEDERATION ON YOUR SERVER FOLLOW THE LINKS ABOVE. IF YOU HAVE A 'SPECIAL' SETUP, OR WANT TO UNDERSTAND HOW IT WORKS, YOU MAY CONTINUE BELOW THIS LINE.

-------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------

Here are some resources that explain the protocol and show how to run a federated "Wave in a Box" wave server:

...

$ ./run-server.sh
.
.
.
Aug 26, 2009 7:02:47 PM org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent processPacket
INFO: received XMPP packet:

<message type="normal" id="4191-2" from="wave.acmewave.com" to="wave.example.com">
<received xmlns="urn:xmpp:receipts"/>
</message>
Aug 26, 2009 7:02:47 PM org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent processMessageReceipt
INFO: got ping response from acmewave.com

<message type="normal" id="4191-2" from="wave.acmewave.com" to="wave.example.com">
<received xmlns="urn:xmpp:receipts"/>
</message>

Chatting

To chat you can now go back and run the client:

$ ./run-client-console.sh <username>

And from From within the client create a new wave and add a participant from another federated server:

/new
/open 0
/add thorogood@acmewave.com

If that user is available they can now chat with you. Server details and times that people are available are posted to the wave-protocoldev@incubator.apache.org mailing list. Post yours too and help test federation.TODO: console client still available? Change mailing list to apache-dev?