Thank you Thomas. You are right. On Thu, Mar 18, 2010 at 6:39 PM, ThomasWrobel <[email protected]> wrote:
> It sounds correct to me, but I'm not 100% sure. > > I do sympathize with the problem of trying to explain Wave to others > though, and how hard it is to find fitting analogies. > I was trying to explain it to someone as being like notice boards, but > perhaps your idea of expressing it as objects in rooms is better. (as > that helps lead to the thinking that you can use different options to > do different things, rather then notice boards which tend to lead to > people thinking it can only be used for that sort of task). > > > On Feb 28, 3:59 pm, badi <[email protected]> wrote: > > It is not easy to describe Wave without falling into the technicality. > > Wave can be loosely described as a communicational labyrinth in which > > rooms can be built by anyone as long as the access and the circulation > > flow between rooms is not hindered. As long as any builder adhere to > > the rules and access control set up by the architect, rooms can be > > added at any given time. > > The labyrinth represents Google Wave federation protocol whereby > > rooms represent Wave Servers and doors represent Wave Clients. > > Different furniture in the rooms represent “waves” and items contained > > in these furniture represents “wavelets”. > > People using the items are called participants. Participants can > be > > invited to share an item. Once invited to share a “shirt” for > > instance, a copy of this shirt is made and sent to each participant's > > room. But, any change made or to be made to the original shirt or to > > its copies must be first approved by the room that hold the original > > shirt. Once approved, change(s) are first applied to the original > > shirt then to all the copies in different rooms. At any given time, a > > participant to the shirt can rewind to see all the changes made to the > > said shirt even if some of them were already deleted or just altered. > > He can see who among the participants deleted them or suggested the > > changes. > > Participants are linked to specific items not to the entire furniture. > > A participant linked to a shirt for instance will always receive > > updates made to the shirt, but he may not even know the existence of > > the T-shirt on the other coat hanger in the same cabinet, unless he > > gets invited to it. A participant can decide to create a new item from > > a copy of the original item. From there on, the original of the newly > > created item will be hosted in the room where the author lives (if he > > is in the different room). > > But, instead of making another shirt from the copy of the original, he > > may decide to make a totally different item, like a pajama. ( I get a > > bit confused here. Will the room with the original shirt know about > > this pajama if none of its guest has been invited to it?) I tend to > > believe that it will not. > > If a room is closed for any reason, these changes will be held in the > > queues and then applied to the copy of the shirt once the room opens > > again. If the room holding the original shirt is permanently closed, > > former participants to the original shirt can still look at the copy > > of the shirt that is held in their respective rooms, but no changes > > can never be made to them. But they can start a totally new shirt by > > copying the old one. > > > > Just needed to know whether this explanation is correct? > > -- > You received this message because you are subscribed to the Google Groups > "Wave Protocol" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<wave-protocol%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
