Hi everyone,
Just a little bit ago we opened the federation port for Google Wave's
developer instance, so we can all begin experimenting with federating waves
against WaveSandbox <http://wavesandbox.com/>.com <http://wavesandbox.com/>.
Since that is the developer preview instance, please keep in mind that it is
an experimental service, and it is likely that there will be unforeseen
glitches in the coming weeks. Please share your progress here in the
wave-protocol forum, so we can work through issues together.
Over the next several weeks we plan to add some important features to this
service:
- TLS for XMPP:
- The protocol itself specifies two distinct security mechanisms:
delta signing and XMPP over TLS. Delta signing is required to be able to
verify the authenticity of the source of the operations. TLS is an
additional layer of security to the XMPP protocol, but it can be
a bit hairy
to configure. In order to encourage prototyping, TLS is not enabled on
WaveSandbox.com, but it will become required in the coming
weeks. This gives
existing FedOne instances an opportunity to get signed certificates and
configure their XMPP servers properly.
- Reliable Delivery:
- For any communication mechanism it is important that there is a
contract for delivery of the message contents, and we are working on a
reliable delivery mechanism from WaveSandbox.com.
With that said, to get started federating with WaveSandbox.com, you should
visit the wave-protocol project <http://code.google.com/p/wave-protocol/> and
review the installation
instructions<http://code.google.com/p/wave-protocol/wiki/Installation>.
If you have previously installed and configured FedOne to talk to
other FedOne instances, you will need to upgrade to the latest revision
(revision 08b5eecb93) to properly interoperate with WaveSandbox.com. For
those of you building your own clients or servers, please take special care
to review the documentation that describes the
errata<http://code.google.com/p/wave-protocol/wiki/DifferencesFromSpecifications>
between
the protocol specification and the current FedOne implementation between the
protocol specification and the current FedOne implementation, and
coincidentally, WaveSandbox.com.
If you don't have a WaveSandbox.com account, you may request a developer
account here <https://services.google.com/fb/forms/wavesignupfordev/>. We
hope to provision those accounts within a week or so.
As you are developing, please keep in mind we welcome contributions to the
growing open source reference implementation; please check out this guide
on submitting open source
code<http://code.google.com/p/wave-protocol/wiki/SubmittingCode>
.
On the specification front, the Google Wave Conversation Model draft
specification has been revised and updated to include the blip document
schema, which defines the representation of rich text necessary for proper
interoperation with WaveSandbox.com. That document is available here:
http://www.waveprotocol.org/draft-protocol-specs/wave-conversation-model
The updated specifications and FedOne code introduce new changes to the wave
model, but they aren't the last; we expect more changes to come as we
iterate with you on the implementation and learn from these early
experiments in federation. Once the specifications and reference code have
converged and become reasonably stable we will begin to federate
wave.google.com, until then we have a lot of work to do. Looking forward to
hearing your feedback.
Cheers,
-Dan
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
