Clarifies a lot, to me. Wavelets are easy to conceptualize.
This link has been bookmarked by 23 people . It was first bookmarked on 29 May 2009, by Tyson Key.
-
25 Jul 09
-
A wave consists of XML documents
-
wave addresses which consist of a user name and a wave provider domain in the same form as an email address, namely <username>@<domain>.
-
A gateway translates between waves and other communication and sharing protocols such as email and IM.
-
Each wavelet has a list of participants, and a set of documents that make up its contents.
-
A wave consists of a set of wavelets.
-
different users have different wave views for a given wave.
-
the user's read/unread state for the wave, is stored in a user-data wavelet in the wave with the user as the only participant.
-
a private reply within a wave, which is represented as a wavelet
-
A wavelet has a wavelet id which is unique within its wave.
-
A wavelet is hosted by the wave provider of the participant who creates the wavelet.
-
Wavelets in the same wave can be hosted by different wave providers.
-
user-data is not federated
-
Each wavelet is a container for any number of documents.
-
Annotations are key-value pairs
-
It is composed of an XML document and a set of annotations.
-
The blips in a wave form a threaded conversation.
-
The central pieces of the wave service is the wave store, which stores wavelet operations, and the wave server, which resolves wavelet operations by operational transformation and writes and reads wavelet operations to and from the wave store.
-
The wave server is responsible for processing the wavelet operations submitted to the wavelet by local participants and by remote participants from other wave providers.
-
a wave provider is "upstream" relative to its local wavelets and that it is "downstream" relative to its remote wavelets.
-
The wave service uses two components for peering with other wave providers, a "federation host" and a "federation remote".
-
The federation host maintains (in persistent storage) a queue of outgoing operations for each remote domain. Operations are queued until their receipt is acknowledged by the receiving federation remote.
-
It is used to push new wavelet operations applied to a local wavelet to the wave providers of any remote participants.
-
<wavelet-update xmlns="http://waveprotocol.org/protocol/0.2/waveserver"
-
<delta-history xmlns="http://waveprotocol.org/protocol/0.2/waveserver"
-
<applied-delta xmlns="http://waveprotocol.org/protocol/0.2/waveserver">
-
<submit-request xmlns="http://waveprotocol.org/protocol/0.2/waveserver">
-
<submit-response xmlns="http://waveprotocol.org/protocol/0.2/waveserver"
-
the operation does not modify the input document
-
A document is a sequence of items, where each item is a character, a start tag, or an end tag. Each item has a key-value map of annotations.
-
After the final component, the annotations update must be empty, and the cursor must be to the right of the last item in the input document.
-
A document operation is a set of instructions that specify how to process an input document, reading its sequence of items from left to right, to generate an output document.
-
-
24 Jul 09
-
16 Jun 09
-
10 Jun 09
-
09 Jun 09
-
07 Jun 09
-
05 Jun 09
-
04 Jun 09
-
Add Sticky NoteWhile the root conversation wavelet of any wave should be located on the WSP indicated through parsing of the wave ID (ala '<domain>:w/<id>', e.g. 'gwave.com:w/fXd23kLp'), further wavelets inside a wave may be hosted on any WSP. The most obvious reasoning for this choice is that a user should primarily contain data - that may only be most relevant to them - within their own WSP. This is most notably the case in terms of private replies, which allow a subset of wave participants to interact privately within the already visualised wave. Private wavelets may also be used for internal participant storage; for example, to store information about what parts of a wave this user has already read.
-
-
Add Sticky Note
2.2. Documents
Each wavelet is a container for any number of uniquely named XML documents. This set of documents are authoritatively located on the WSP that provides the given wavelet, and can not span between providers or be rehomed into alternative wavelets. To support this idiom, any single document operation may only target a single wavelet. The actions within this operation may optionally effect a single part of the contained set, but can not effect documents outside the target wavelet.
For background, however, a wavelet will contain a root document along with potentially any number of other documents arranged in a heirarchical-like conversation structure
-
Flexible enough but clear bounds.
-
-
-
01 Jun 09
-
documentstartannotation
-
mark-up of a ranged annotation
-
extension to XML used within the Google Wave Federation Protocol
-
may span across normal XML tag boundaries
-
documentendannotation
-
-
30 May 09
-
29 May 09
Public Stiky Notes
Page Comments
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.