Quick followup questions: I just set up my federated server over the weekend, so I suspect it may be the latest. (I'm using Openfire and followed the install directions linked to below). However, I have two questions.
First, how do I determine the revision? My build.properties tells me that I am running fedone.version=0.2 but I can't find revision numbers anything like 08b5eecb93. Second question: I've set up my server, opened the proper ports, and connected using the run-console-client from a remote machine. However, I haven't been able to test with other servers yet, and I'm curious about if besides finding other servers to federate with, there are things that need to be done in the configuration or build of the server, or if it will just federate out of the current build without any special configuration concerns. Aldon -----Original Message----- From: [email protected] [mailto:[email protected]]on Behalf Of Dan Peterson Sent: Monday, November 02, 2009 1:18 PM To: wave-protocol Subject: Google Wave Federation Protocol port open on WaveSandbox.com and Other Updates 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.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: a.. TLS for XMPP: a.. 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. b.. Reliable Delivery: a.. 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 and review the installation instructions. 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 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. 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. 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 -~----------~----~----~----~------~----~------~--~---
