Google Wave: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
m →‎Open source: Satisfied the citation needed tag, maybe it should just be removed though.
Tag: shouting
Line 27: Line 27:
'''Google Wave''' is "a personal communication and collaboration tool" announced by [[Google]] at the [[Google I/O]] conference on May 27, 2009.<ref>[[TechCrunch]] (May 28, 2009): [http://www.techcrunch.com/2009/05/28/google-wave-drips-with-ambition-can-it-fulfill-googles-grand-web-vision/ Google Wave Drips With Ambition. A New Communication Platform For A New Web.]</ref><ref name="iokeynote">{{cite web|url=http://www.youtube.com/watch?v=v_UyVmITiYQ|title=I/O Conference Google Wave Keynote|publisher=Google}}</ref> It is a [[web application|web-based service]], [[computing platform]], and [[protocol (computing)|communications protocol]] designed to merge [[e-mail]], [[instant messaging]], [[wiki]], and [[social networking]].<ref name="aboutgw">{{cite web|url=http://wave.google.com/help/wave/about.html|title=About Google Wave|publisher=Google}}</ref> It has a strong [[Collaborative software|collaborative]] and [[real-time]]<ref name="gwdevblog">{{cite web|url=http://googlewavedev.blogspot.com/2009/05/introducing-google-wave-apis-what-can.html|title=Google Wave Developer Blog|publisher=Google}}</ref> focus supported by extensions that can provide, for example, robust [[spellchecker|spelling/grammar checking]], automated translation between 40 languages,<ref name="iokeynote" /> and numerous other extensions.<ref name="gwdevblog" /> It was announced in Google's official blog on July 20, 2009, that the preview of Google Wave would be extended to about 100,000 users on September 30, 2009.<ref>{{cite web|url=http://googlewavedev.blogspot.com/2009/07/google-wave-updates-from-todays.html|title=Updates from todays hackathon|publisher=Google}}</ref>
'''Google Wave''' is "a personal communication and collaboration tool" announced by [[Google]] at the [[Google I/O]] conference on May 27, 2009.<ref>[[TechCrunch]] (May 28, 2009): [http://www.techcrunch.com/2009/05/28/google-wave-drips-with-ambition-can-it-fulfill-googles-grand-web-vision/ Google Wave Drips With Ambition. A New Communication Platform For A New Web.]</ref><ref name="iokeynote">{{cite web|url=http://www.youtube.com/watch?v=v_UyVmITiYQ|title=I/O Conference Google Wave Keynote|publisher=Google}}</ref> It is a [[web application|web-based service]], [[computing platform]], and [[protocol (computing)|communications protocol]] designed to merge [[e-mail]], [[instant messaging]], [[wiki]], and [[social networking]].<ref name="aboutgw">{{cite web|url=http://wave.google.com/help/wave/about.html|title=About Google Wave|publisher=Google}}</ref> It has a strong [[Collaborative software|collaborative]] and [[real-time]]<ref name="gwdevblog">{{cite web|url=http://googlewavedev.blogspot.com/2009/05/introducing-google-wave-apis-what-can.html|title=Google Wave Developer Blog|publisher=Google}}</ref> focus supported by extensions that can provide, for example, robust [[spellchecker|spelling/grammar checking]], automated translation between 40 languages,<ref name="iokeynote" /> and numerous other extensions.<ref name="gwdevblog" /> It was announced in Google's official blog on July 20, 2009, that the preview of Google Wave would be extended to about 100,000 users on September 30, 2009.<ref>{{cite web|url=http://googlewavedev.blogspot.com/2009/07/google-wave-updates-from-todays.html|title=Updates from todays hackathon|publisher=Google}}</ref>


GOOGLE WAVE DOESN'T WORK! STAY AWAY!
== Etymology ==
The name was inspired by the ''[[Firefly (TV series)|Firefly]]'' television series<ref name="itnewsau"></ref> in which a ''Wave'' is an electronic communication (often consisting of a [[video call]] or video message).<ref name="itnewsau">{{cite news | first = Nate | last = Cochrane | url = http://www.itnews.com.au/News/104396,opinion-googles-wave-drowns-the-bling-in-microsofts-bing.aspx | title = Opinion: Google's wave drowns the bling in Microsoft's Bing | agency = iT News Australia | date = May 29, 2009 | accessdate = June 3, 2009}}</ref> During the developer preview, a number of references were made to the series such as [[Lars_Rasmussen_(Software_Developer)|Lars Rasmussen]] replying to a message with "shiny", a word commonly used in the series to mean ''cool'' or ''good'', and the crash message of Wave being a popular quotation from the series: "Curse your sudden but inevitable betrayal!".<ref name="iokeynote" /><ref>originally said by [[List of characters in the Firefly universe#Hoban Washburne|Wash]] at 6:36, in ''[[Serenity (Firefly episode)|Serenity]]''; [[Firefly (TV series)|Firefly]]: The Complete Series (Blu-ray), 2008, 20th Century Fox</ref>


==Product==
==Product==

Revision as of 18:35, 2 October 2009

Google Wave
Developer(s)Google
Repositorynone Edit this at Wikidata
PlatformCross-Platform
TypeWeb application/protocol
LicenseApache License (only Google Wave Federation Prototype Server and ConsoleClient)
Websitewave.google.com

Google Wave is "a personal communication and collaboration tool" announced by Google at the Google I/O conference on May 27, 2009.[1][2] It is a web-based service, computing platform, and communications protocol designed to merge e-mail, instant messaging, wiki, and social networking.[3] It has a strong collaborative and real-time[4] focus supported by extensions that can provide, for example, robust spelling/grammar checking, automated translation between 40 languages,[2] and numerous other extensions.[4] It was announced in Google's official blog on July 20, 2009, that the preview of Google Wave would be extended to about 100,000 users on September 30, 2009.[5]

GOOGLE WAVE DOESN'T WORK! STAY AWAY!

Product

Google Wave is designed as the next generation of Internet communication. It is written in Java using OpenJDK; its web interface uses the Google Web Toolkit. Instead of sending a message and its entire thread of previous messages or requiring all responses to be stored in each user's inbox for context, objects known as waves contain a complete thread of multimedia messages (blips) and are located on a central server. Waves are shared and collaborators can be added or removed at any point during a wave's existence.

Waves, described by Google as "equal parts conversation and document", are hosted XML documents that allow seamless and low latency concurrent modifications.[6] Any participant of a wave can reply anywhere in the message, edit the content and add participants at any point in the process. Users can reply to blips within waves. Recipients are notified of changes/replies in all waves they are active in and then view the changes when they subsequently access a given wave. In addition, waves are live. All replies/edits are seen real-time, letter by letter, as they are typed by the other collaborators. Multiple participants may edit a single wave simultaneously in Google Wave. Thus, waves not only can function as e-mail and threaded conversations but also as an instant messaging service, merging the functions of e-mail and instant messaging. It depends only on whether both users are online at the same time or not, allowing a wave to even shift repeatedly between e-mail and instant messaging depending on the user's needs. The ability to show messages as they are typed can also be disabled, similar to conventional instant messaging.[3]

The ability to modify a wave at any location lets users create collaborative documents, edited in a manner akin to wikis.

The history of each wave is stored within it. Collaborators may use a playback feature in Google Wave to observe the order which a wave was edited, blips were added, and who was responsible for what in the wave.[3][4] The history may 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]

Google Wave is still in active development. It is expected to continue to be so until later in 2009,[2] launching to about 100,000 users on[7] 30th September. Google Wave access can be requested. Developers have been given access to Wave proper, and all wave users invited by Google can invite up to 8 others. Those who receive indirect invitations (were invited by someone who was invited by Google) will not be able to invite others. As of October 1st, Google Wave testers were unable to add extensions[8] because "settings" is under construction.

Open source

Google plans to release most of the source code as open source[2], allowing the public to develop its features through extensions.[2] Google will also allow third-parties to build their own Wave services as quickly as possible (be it private or commercial) because it wants the Wave protocol to replace the e-mail protocol.[2][9][10] Initially, Google will be the only Wave service provider, but it is hoped that, as the protocol becomes standardized and the prototype server becomes stable, other service providers will launch their own Wave services, possibly designing their own unique web-based clients as is common with many email service providers. The possibility also exists for native Wave clients to be made, as demonstrated by Google with their CLI-based console client.[11]

Google has made an initial open-source release of some components of Wave:[12]

  1. the operational transform (OT) code,
  2. the underlying wave model, and
  3. a basic client/server prototype that uses the wave protocol

In addition, Google has provided some detail about the next phases of the open-source release:[11]

  1. 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
  2. a testing and verification suite for people who want to do their own implementation (for example, for porting the code to other languages)

API

Google is building APIs that allow developers to use and build on Google Wave by way of:

  • Extensions, program robots to automate common tasks and/or build gadgets to extend or change user interaction (i.e., posting blips on microblog feeds or providing RSVP recording mechanisms).[2][3][13]
  • Embed, dropping interactive windows into a given wave on external site, blogs, et cetera.[2][13]

Protocol

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.[14] 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.[2][9][10] In this way, Google intends to only be one of many wave providers.[2][9][10] 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.[9][10] The protocol allows private reply wavelets within parent waves, where other participants have no access or knowledge of them.[9][10]

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.

See also

References

  1. ^ TechCrunch (May 28, 2009): Google Wave Drips With Ambition. A New Communication Platform For A New Web.
  2. ^ a b c d e f g h i j k "I/O Conference Google Wave Keynote". Google.
  3. ^ a b c d "About Google Wave". Google.
  4. ^ a b c "Google Wave Developer Blog". Google.
  5. ^ "Updates from todays hackathon". Google.
  6. ^ http://www.waveprotocol.org/whitepapers/operational-transform
  7. ^ http://www.techcrunch.com/2009/07/21/google-wave-begins-to-swell-with-developers-wider-release-this-september/
  8. ^ http://www.freelancesocialmedia.com/google-wave-thoughts-after-an-hour-of-testing/
  9. ^ a b c d e http://www.waveprotocol.org/whitepapers/google-wave-architecture
  10. ^ a b c d e http://www.waveprotocol.org/whitepapers/internal-client-server-protocol
  11. ^ a b "Google Wave Federation Protocol and Open Source Updates". Google.
  12. ^ "Google Wave Federation Protocol and Open Source Updates". Google.
  13. ^ a b "Google Wave API - Google Code". Google.
  14. ^ "Google Wave Federation Protocol". Google.

External links