Google Wave is a software framework centered on online real-time collaborative editing, previously developed by Google It was first announced at the Google I/O conference on May 27, 2009. Google Wave is a web-based computing platform and communications protocol, designed to merge key features of media like e-mail, instant messaging, wikis, and social networking.[4Communications using the system can be synchronous and/or asynchronous, depending on the preference of individual users. Software extensions provide contextual spelling/grammar checking, automated translation among 40 languages, and numerous other features.
Initially released only to developers, a preview release of Google Wave was extended to 100,000 users in September 2009, each allowed to invite additional users. Google accepted most requests submitted starting November 29, 2009, soon after the September extended release of the technical preview. On May 19, 2010, Google Wave was released to the general public.
On August 4, 2010, Google announced the suspension of stand-alone Wave development and the intent of maintaining the web site at least for the remainder of the year. Development was handed over to the Apache Software Foundation who started to develop a server based product called Wave in a box.
Visit the URL for Google Wave:
http://en.wikipedia.org/wiki/File:Googlewave.svg
Google Wave provides federation using an extension of XMPP, the open Wave Federation Protocol. Being an open protocol, anyone can use it to build a custom Wave system and become a wave provider. The use of an open protocol is intended to parallel the openness and ease of adoption of the e-mail protocol and, like e-mail, allow communication regardless of provider. Google hopes that waves may replace e-mail as the dominant form of Internet communication. In this way, Google intends to be only one of many wave providers. It can also be used as a supplement to e-mail, instant messaging, FTP, etc.
A key feature of the protocol is that waves are stored on the service provider's servers instead of being sent between users. Waves are federated; copies of waves and wavelets are distributed by the wave provider of the originating user to the providers of all other participants in a particular wave or wavelet so all participants have immediate access to up-to-date content. The originating wave server is responsible for hosting, processing, and concurrency control of waves.The protocol allows private reply wavelets within parent waves, where other participants have no access or knowledge of them.
No comments:
Post a Comment