When Google announced that several programmer interfaces have been deprecated from the API Directory, the development community reacted loudly and in force. While some APIs on the list will be deprecated with no shut down date announced, others like the Translate API will be shut down at the end of the year.
The Google Wave Robots API v2 is not backward compatible with version 1 and has been enhanced with new features like: Active API, Context, Filtering, Error Reporting, Proxying-For. Beside a Java and a Python client library useful to create robots, developers can build their own libraries based on the Robot Wire Protocol.
With the consumer release of Google Wave scheduled for the 30th of September, InfoQ had a Q&A with Google Software Engineer Dhanji Prasanna about some of its less known internals, details about how it’s being developed by the Google engineers and best practices.
With the Google Wave Preview scheduled for public availability on September 30th, Wave API Tech Lead Douwe Osinga has posted on the Wave Google Group about what the team has been working on along with some future directions.
The recently announced Google Wave platform, which is promoting HTML 5, is believed by some to have a major impact on RIA, including Silverlight, while others consider that Wave is actually a competitor for Microsoft’s SharePoint and Exchange rather than RIA. It's poll time.
Google Wave is three things: a tool, a platform and a protocol. The architecture has at its heart the Operational Transformation (OT), a theoretical framework meant to support concurrency control.
Google has announced two more tools that will help in its mission “to organize the world's information and make it universally accessible and useful”. One of them is version 2.0 of its Chrome browser which aims to facilitate demanding client-side applications and the other one is Wave, a new environment for communication and collaboration on the Web.
