There is an open federation port on wavesandbox. See the earlier post in this group.
regards, Jochen Bekmann On Wed, Nov 25, 2009 at 6:11 PM, Koala Yeung <[email protected]> wrote: > > Hi, > > This is the end of November. > Are there any news on the protocol? > > > Koala Yeung > > > On 10月1日, 下午5時53分, Dan Peterson <[email protected]> wrote: >> Hey folks, >> >> Given the recent push to open up the preview of Google Wave to users >> (http://googleblog.blogspot.com/2009/09/surfs-up-wednesday-google-wave...), >> we wanted to take a moment to provide an update on the overall federation >> protocol effort. >> >> Short summary: >> >> We're continuing to work to open up a server-to-server federation port on >> WaveSandbox <http://wavesandbox.com/>.co >> <http://wavesandbox.com/>m<http://wavesandbox.com/>, >> but, due to production pressures related to our recent preview release, we >> are now planning to enable it towards the end of October. We've also been >> working to provide more documentation around the wave model, and so we've >> produced a draft specification for the wave conversation model: <LINK> >> >> Getting deeper into the details: >> >> As a number of you in this forum have already noted, we've added support for >> agents to FedOne. Agents are the underlying infrastructure for robots as in >> the Google Wave APIs >> (http://code.google.com/apis/wave/extensions/robots/index.html). The first >> agent we created was "Echoey" which proved useful for debugging federation. >> As the name implies that whenever added to a wave will echo a response. >> Check it out >> at:http://code.google.com/p/wave-protocol/source/browse/src/org/waveprot... >> . >> >> In order for us to be able to federate WaveSandbox <http://wavesandbox.com/> >> .co <http://wavesandbox.com/>m <http://wavesandbox.com/> we have updated our >> production systems to support the operations as used in FedOne. This took us >> a significant step closer to supporting federation. We expect to make a few >> small changes to FedOne in order to allow it to federate with >> WaveSandbox<http://wavesandbox.com/> >> .com <http://wavesandbox.com/>. >> >> Please note that once we start federating >> WaveSandbox<http://wavesandbox.com/> >> .co <http://wavesandbox.com/>m <http://wavesandbox.com/>, this will be an >> experimental service. This means that we will not have 100% uptime, and will >> likely still contain bugs. We also expect that have to perform data >> migrations on waves and enhance the federation protocol to allow for more >> efficient signing of deltas. >> >> Beyond the changes listed in the Google Wave Conversation model roadmap, the >> federation protocol will continue to change over the course of the coming >> months as well. We are working through some of the quirks in our production >> system, including sunsetting some unnecessary (internal) operations, >> specifying the format of URIs, and improving ID generation in waves. Given >> the cryptographic authentication measures in the federation protocol, once a >> wave has been generated (and thus signed), it becomes impossible to migrate >> its contents from one underlying format to another. In order to avoid >> trapping user data in obsolete formats, the federation port on >> wave.google.com is gated on many of the above items. >> >> The draft Google Wave Conversation Model specification mentioned above goes >> into significant detail about the XML-like format of documents stored in >> wavelets. You will note that the FedOne client does not use the document >> schema as published above. We expect the FedOne client to only provide >> limited support for the new document schema initially. Nonetheless, we >> encourage you to inspect it as this is where we are heading. >> >> Please take a look at the new spec, and let us know what you think. >> >> 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 > -~----------~----~----~----~------~----~------~--~--- > > -- 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.
