Google Wave
Apache Software Foundation, Google | |
Initial release | May 28, 2009 |
---|---|
Preview release | 0.4-rc10
/ October 10, 2014 |
Apache License 2.0 | |
Website | incubator |
Google Wave, later known as Apache Wave, was a software framework for
Wave is a
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, it was released to the general public.[6]
On August 4, 2010,
History
Etymology
The science fiction television series
During an event in Amsterdam, Netherlands,[15] it became apparent that the 60-strong team that was then working on Wave in Sydney used Joss Whedon-related references to describe, among others, the sandbox version of Wave called Dollhouse after the TV series by Firefly producer Joss Whedon, which was aired on Fox in the US. The development of external extensions was codenamed "Serenity", after the spaceship used in Firefly and Serenity.
Free software
Google released most of the source code as free software,[2] allowing the public to develop its features through extensions.[2] Google allowed third parties to build their own Wave services (be it private or commercial) because it wanted the Wave protocol to replace the e-mail protocol.[2][16][17] Initially, Google was the only Wave service provider, but it was hoped that other service providers would launch their own Wave services, possibly designing their own unique web-based clients as is common with many email service providers. The possibility also existed for native Wave clients to be made, as demonstrated with their CLI-based console client.[18]
Google released initial free software components of Wave:[19]
- the operational transformation (OT) code,
- the underlying wave model, and
- a basic client/server prototype that uses the wave protocol
In addition, Google provided some detail about later phases of the free software release:[18]
- wave model code that is a simplified version of Google's production code and is tied to the OT code; this code will evolve into the shared code base that Google will use and expects that others will too
- a testing and verification suite for people who want to do their own implementation (for example, for porting the code to other languages)
Features
Google Wave was a new Internet
Waves, described by Google as "equal parts conversation and document", were hosted
The ability to modify a wave at any location let users create collaborative documents, edited in a manner akin to wikis. Waves could easily link to other waves. In many respects, it was a more advanced forum.[21] It could be read and known to exist by only one person, or by two or more and could also be public, available for reading and writing to everyone on the Wave.[22][citation needed]
The history of each wave was stored within it. Collaborators could use a playback feature to observe the order in which it was edited, blips that were added, and who was responsible for what in the wave.[4][5] The history could also be searched by a user to view and/or modify specific changes, such as specific kinds of changes or messages from a single user.[2]
Reception
During the initial launch of Google Wave, invitations were widely sought by users and were sold on auction sites.[23] Those who received invitations and decided to test Google Wave could not communicate with their contacts on their regular email accounts. The initial spread of Wave was very restricted.
Google Wave initially received positive press coverage for its design[24] and potential uses.[25][26] After its demise, it was criticized for trying to merge "all forms of communication in a single, crowded space".[27]
End of development of Google Wave
![](http://upload.wikimedia.org/wikipedia/commons/thumb/2/24/Wikinews-logo.svg/40px-Wikinews-logo.svg.png)
On August 4, 2010, Google announced Wave would no longer be developed as a stand-alone product due to a lack of interest.[28] Google's statement surprised many in the industry and user community.
Google later clarified the Wave service would be available until April 2012, giving users the opportunity to use the export functionality to keep a local copy of their waves in PDF format.[29]
Response to the news of the end of development came from Wave users in the form of a website.[30] After their announcement in early August 2010, the website recorded over 49,000 supporter registrations urging Google Wave's continuation.[31]
In retrospect, the lack of success of Google Wave was attributed among other things to its complicated user interface resulting from a product that merged features of email, instant messengers and wikis but ultimately failed to do anything significantly better than the existing solutions.[32]
Chris Dawson of online technology magazine
Apache Wave
Google Wave was accepted by the
Wave in a Box
![](http://upload.wikimedia.org/wikipedia/en/f/f7/Wave_in_a_Box_logo.png)
Wave in a Box is the current server implementation of Apache Wave. Currently, there are no demo servers available.[35]
Crisis and SwellRT
In 2016, several discussions took place within the Apache Wave community, aiming to tackle the stagnation and crisis state of the project. The Apache Software Foundation mentor of Apache Wave, Upayavira,[36] was concerned by the project's stagnation, but framed SwellRT (a fork which re-engineered Wave into a backend-as-a-service for building apps) as Wave's potential savior.[37] Eventually, Wave was approved to continue within Apache incubator program, and a copy of SwellRT codebase was placed in the Apache Wave repository in order to grant the Wave community access to it.[38] In this regard, Intellectual Property of SwellRT was transferred to the Apache Foundation in 2017.[39] Still this was not sufficient to resurrect Wave's developer community, and SwellRT continued as independent project.
Retirement
The Wave project retired on January 15, 2018, having never left incubator status.[40]
Extension programming interface
Google Wave is extensible through an
The last version of robots API is 2.0.[42]
Google Wave also supports extension installers, which bundle back-end elements (robots and gadgets) and front-end user interface elements into an integrated package. Users may install extensions directly within the Wave client using an extension installer.
Extensions
Google Wave extensions are
Over 150 Google Wave extensions have been developed either in the form of Gadgets or Robots.[43]
Robots
A robot is an automated participant on a wave. It can read the contents of a wave in which it participates, modify its contents, add or remove participants, and create new blips or new waves. Robots perform actions in response to events. For example, a robot might publish the contents of a wave to a public blog site and update the wave with user comments.
Robots may be added as participants to the Wave itself. In theory, a robot can be added anywhere a human participant can be involved.
Gadgets
Gadget extensions are applications that run within the wave, and to which all participants have access. Robots and Gadgets can be used together, but they generally serve different purposes. A gadget is an application users could participate with, many of which are built on Google's OpenSocial platform. A good comparison would be iGoogle gadgets or Facebook applications.
The gadget is triggered based on the user action. They can be best described as applications installed on a mobile phone. For example, a wave might include a sudoku gadget that lets the wave participants compete to see who can solve the puzzle first.
Gadgets may be added to individual waves and all the participants share and interact with the gadget.
Federation protocol
Google Wave provides
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.[16][17] The protocol allows private reply wavelets within parent waves, where other participants have no access or knowledge of them.[16][17]
Security for the communications is provided via Transport Layer Security authentication, and encrypted connections and waves/wavelets are identified uniquely by a service provider's domain name and ID strings. User-data is not federated, that is, not shared with other wave providers.
Adoption of Wave Protocol and Wave Federation Protocol
Besides Apache Wave itself, there were other open-source variants of servers and clients with different percentage of Wave Federation and Wave Protocol support. Wave was re-engineered into a backend-as-a-service solution by the
.Compatible third-party servers
The following servers were compatible with the Google Wave protocol:
- social movements needs.[47]
- Novell Vibe, formerly known as Novell Pulse.[48]
- Rizzoma is a platform for collaborative work in real time. It allows communication within a certain context permitting a chat to instantly become a document where topics of a discussion organized into branches of mind-map diagram and minor details are collapsed to avoid distraction. The user is able to sign in using a Google or Facebook account and choose whether your topics are private or public.[49]
- SAP StreamWork is a collaboration decision making service.[50][51]
- SwellRT is a backend-as-a-service for building collaborative and federated apps. It is a fork which re-engineered Apache Wave, and was adopted within the Apache Wave project.[52]
See also
References
- ^ TechCrunch (May 28, 2009): Google Wave Drips With Ambition. A New Communication Platform For A New Web.
- ^ a b c d e f g h i j k Google Inc. "I/O Conference Google Wave Keynote". YouTube.
{{cite web}}
:|author=
has generic name (help) - ^ Google Inc. (2009). "Google Wave Overview". Archived from the original on April 27, 2010.
[A] new web application for real-time communication and collaboration.
{{cite web}}
:|author=
has generic name (help) - ^ a b c d Google Inc. "About Google Wave".
{{cite web}}
:|author=
has generic name (help) - ^ a b "Google Wave Developer Blog".
- ^ Shankland, Stephen. (May 19, 2010) Google Wave: Now open to the public | Deep Tech – CNET News Archived September 14, 2013, at the Wayback Machine. News.cnet.com. Retrieved on 2010-12-14.
- ^ Official Google Blog: Update on Google Wave. Googleblog.blogspot.com (April 8, 2010). Retrieved on 2010-12-14.
- ^ "Official Blog: More spring cleaning out of season". Googleblog.blogspot.com. November 22, 2011. Retrieved June 15, 2013.
- ^ Meyer, David. (September 3, 2010) Google puts open-source Wave in a 'box' | Application Development | ZDNet UK. Zdnet.co.uk. Retrieved on 2010-12-14.
- ^ Google Wave inte ute ur leken. IDG.se. Retrieved on December 14, 2010.
- ^ Murphy, David. (January 1, 1970) Google Spins Wave Into 'Wave in a Box' for Third-Party Use | News & Opinion. PCMag.com. Retrieved on 2010-12-14.
- ^ "Wave Incubation Status - Apache Incubator". incubator.apache.org. Retrieved April 12, 2018.
- ^ a b Cochrane, Nate (May 29, 2009). "Opinion: Google's wave drowns the bling in Microsoft's Bing". IT News Australia. Archived from the original on June 3, 2009. Retrieved June 3, 2009.
- : The Complete Series (Blu-ray), 2008, 20th Century Fox.
- ^ Rottmann, Ralf (October 30, 2009). "Google Wave to be opened for federation today!". The Next Web.
- ^ a b c d e Google Wave Federation Architecture – Google Wave Federation Protocol Archived March 30, 2013, at the Wayback Machine. Waveprotocol.org. Retrieved on December 14, 2010.
- ^ a b c d e Google Wave Client-Server Protocol – Google Wave Federation Protocol Archived March 30, 2013, at the Wayback Machine. Waveprotocol.org. Retrieved on December 14, 2010.
- ^ a b "Google Wave Federation Protocol and Open Source Updates".
- ^ "Google Wave Federation Protocol and Open Source Updates".
- ^ Google Wave Operational Transformation – Google Wave Federation Protocol Archived May 31, 2009, at the Wayback Machine. Waveprotocol.org. Retrieved on December 14, 2010.
- ^ Google Wave Review. VariableGHz (October 13, 2009). Retrieved on 2010-12-14.
- ^ "What Is Web 3.0 (Web3)? Definition, Guide and History". WhatIs. Retrieved December 12, 2023.
- ^ Google Wave Invite Selling for $70 on eBay
- ^ B.B.C. report introducing Google Wave in September 2009
- ^ Google Wave to get its own App Store (Engadget)
- ^ "CNET Predictions for 2010". Archived from the original on January 17, 2010. Retrieved January 13, 2010.
- ^ "What in the Hell Was Google Wave Trying to Be Anyway?". Gizmodo. May 27, 2019. Retrieved March 18, 2023.
- ^ a b ZDNet on GW's death
- ^ "Status of Google Wave - Google Help". Retrieved May 16, 2024.
- ^ "'"Save Google Wave" Site Forms'". Archived from the original on August 15, 2010. Retrieved August 11, 2010.
- ^ Save Google Wave! Archived August 5, 2018, at the Wayback Machine. Retrieved on May 14, 2011.
- ^ Google Wave: why we didn't use it, Ars Technica
- ^ North, Alex. (December 6, 2010) Google Wave Developer Blog: Introducing Apache Wave. Googlewavedev.blogspot.com. Retrieved on 2010-12-14.
- ^ WaveProposal – Incubator Wiki. Wiki.apache.org (November 24, 2010). Retrieved on 2010-12-14.
- ^ "Wave in a Box demo servers". Apache Software Foundation. Retrieved October 10, 2012.
- ^ "Wave Incubation Status - Apache Incubator". incubator.apache.org. Retrieved October 28, 2017.
- ^ "September2016 - Incubator Wiki". wiki.apache.org. Retrieved October 28, 2017.
- ^ "December2016 - Incubator Wiki". wiki.apache.org. Retrieved October 28, 2017.
- ^ "March2017 - Incubator Wiki". wiki.apache.org. Retrieved October 28, 2017.
- ^ "Wave Incubation Status - Apache Incubator". Apache Software Foundation. Retrieved January 17, 2018.
- ^ a b "Google Wave API – Google Code".
- ^ "Introducing Robots API v2: The Rise of Active Robots".
- ^ Google Wave Samples Gallery Archived April 15, 2010, at the Wayback Machine. Wave-samples-gallery.appspot.com. Retrieved on December 14, 2010.
- ^ "Google Wave Federation Protocol". Archived from the original on May 30, 2009. Retrieved May 28, 2009.
- ^ Novell Vibe cloud service. Novell.com. Retrieved on December 14, 2010.
- ^ Elliott, Timo. (October 19, 2009) SAP's Gravity Prototype: Business Collaboration Using Google Wave Archived March 24, 2010, at the Wayback Machine. Cloudave.com. Retrieved on 2010-12-14.
- ^ "Kune Homepage". Retrieved April 22, 2012.
- ^ Novell Vibe. Novell.com (December 31, 2009). Retrieved on 2010-12-14.
- ^ "Rizzoma Homepage". Retrieved May 9, 2012.
- ^ Williams, Alex. (May 17, 2010) SAP StreamWork Integrates With Google Wave – ReadWriteCloud. Readwriteweb.com. Retrieved on 2010-12-14.
- ^ How It Works | SAP® StreamWork™ Archived December 8, 2010, at the Wayback Machine. Sapstreamwork.com. Retrieved on December 14, 2010.
- ^ "SwellRT homepage". SwellRT. Retrieved December 17, 2017.
External links
![](http://upload.wikimedia.org/wikipedia/en/thumb/4/4a/Commons-logo.svg/30px-Commons-logo.svg.png)