Hi, As was previously posted (http://groups.google.com/group/wave-protocol/browse_thread/thread/96e7c637c2332881), we've opened up an experimental federation port on our developer instance, wavesandbox.com. We've noticed that a number of people have been federating with wavesandbox with varying degrees of success, and so, we'd like to provide some more details about how things are going:
Part of the federation protocol requires that deltas exchanged between federation providers must be signed by a private key for the originating domain, and that key must be certified by a recognized Certificate Authority. This requirement is a fundamental part of wave's security model, and thus needs to be honoured to protect user-data integrity. We recognize that configuring a FedOne server, obtaining the signed certificates, and getting them into the correct format can be a non-trivial exercise. While there is some basic documentation about certificates for federation, we will be posting more detailed instructions on this shortly -- we'd welcome your comments on suggestions that improve this process -- http://code.google.com/p/wave-protocol/wiki/Certificates Since opening up this port, we've experienced a few new issues in our production environment. Based on our testing, it is likely these issues make federating against wavesandbox.com unreliable. There are at least 3 issues which we have identified so far, which are listed in the issue tracking system: - Google Wave Server does not always federate local wavelets - http://code.google.com/p/wave-protocol/issues/detail?id=54 - Google's Wave Server (sometimes) cannot request missing history - http://code.google.com/p/wave-protocol/issues/detail?id=52 - Google Wave Server does not always commit wavelets - http://code.google.com/p/wave-protocol/issues/detail?id=51 We've been working hard to open up this port for your experimentation, and we'll continue to improve the service as we go. Please understand that it'll likely take a few days to debug and fix some of the outstanding issues (for one, allowing us to catch up on some sleep). We are very grateful for those developers that are jumping in, providing detailed bug reports, and helping work through issues. We hope you bear with us as we deal with the teething problems, and we appreciate your enthusiasm for wave federation -- even at this experimental stage. regards, Jochen Bekmann Engineer, Google Wave --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
