SAN FRANCISCO (MarketWatch) -- Google Inc. said Wednesday that it's killing its "Google Wave" messaging and social-networking service, because of a lack of user interest.
Ribbit - Google Wave - 0 views
- Create an audio connection with multiple Wave participants
- Add non-Wave participants to the session
- Mute or hold any of the individual participants from the stream
- Disconnect any participants from the stream
- End the session
Ribbit Conference Gadget -BetaThe Ribbit Conference Gadget allows Wave participants to escalate an online collaboration session to a real-time audio communications session, allowing participants to talk with each other while collaborating. The Ribbit Conference Gadget is persistent in the Wave and allows any Wave participant to:
Wave is a new way to build distributed applications, and it will open the door to an explosion of innovation.
So, if Wave is not just the demo application, what is it?
Google Wave is a platform for creating distributed applications. Each Wave server can be involved in a number of conversations involving Wavelets, what most people would think of as a document. Wavelets are actually a much more powerful and general because they are based on XML, which means you can have lots of depth of content, like headings and subheadings of a book, but on steroids. Adding a document repository to XMPP is just revolutionary.
The XMPP protocol manages the communication between the Wave servers so that all the Wavelets can synchronize as they are changed. Then Google finished the job by making Wavelets tag-able, searchable and versioned, so you can play back changes.
But Google Wave goes beyond just managing the content--it also manages the programs that act on the content. At any level, a program can be assigned to a Wavelet to render it, that is, show it to a user and help manage the conversation. Google Wave also manages the distribution and management of these programs. The idea of a platform that combines management of the data and the code is really powerful.
Without a doubt, the product that has the entire web buzzing right now is Google Wave (), the search giant’s newly announced communication platform. Earlier this week, we brought you detailed information on the new Google () product in our article Google Wave: A Complete Guide, but now we want to explore exactly why everyone is so excited about Google Wave.
You’ve probably heard people talk about Google Wave being a game-changer, a disruptive product, or maybe even as an email killer. But while keywords and phrases like these grab people’s attention, they don’t explain why or how Google Wave could be a paradigm-shifter. In this article, we explore these questions by highlighting some of Google Wave’s most unique and promising features. By exploring these features, we can better understand the potential of this new technology.
InfoQ: Google Wave's Architecture - 0 views
This is the crucial part of Wave’s technology. Google Wave makes extensive use of Operational Transformations (OT) which are executed on the server. When an user edits a collaborative document opened by several users, the client program provides an Optimistic UI by immediately displaying what he/she types but it also sends the editing operation to the server to be ratified hoping that it will be accepted by the server. The client waits for the server to evaluate the operation and will cache any other operations until the server replies. After the server replies, all cached operations are sent from client to server in bulk. The server, considering operations received from other clients, will transform the operation accordingly and will inform all clients about the transformation, and the clients will update their UI accordingly. Operations are sent to the server and propagated to each client on a character by character basis, unless it is a bulk operation. The server is the keeper of the document and its version is considered the “correct” version. In the end, each client will be updated with the final version received from the server, which is the result of possibly many operational transformations. There are recovery means provided for communication failure or server/client crash. All XML documents exchanged between the client and the server carry a checksum for rapid identification of miscommunications.