(English) A New year starts and this one will be the year of Google Wave. In this new post we talk about what we expect about Google Wave and everything related.
In this post we will introduce the Federation concept.
Federation is the protocol used for the servers to be able to connect their own users with other servers. The Federation lets Wave be a decentralized platform, or in other words, anyone has the chance to create his own servers. This servers will share waves between them. This will allow different networks to share the data that the users choose, fast and on real time.
A wave is nothing but an envelope that among other information stores wavelets. A wavelet can store documents, pictures, and any kind of data. The copies of the wavelets are shared between the wave servers that has at least one participant. One of this server will be the hosting server of the wave.
With this definition of ‘wave’ we can see that a wave is not an indivisible element, a wave is a set of elements called wavelets. When a user wants to open a wave, he recieves a view of the wavelets that he is participant. This makes that each user might have a different view of the same wave. With this feature we can make easily private messages restricting the users that can have access to the wavelet. Some documents represent rich text messages in the wavelet, these are called “blips”.
To identify them, each wave has an unique identifier and domain. The domain is the server domain.
As we know, waves are stored in different servers. But what the servers really share are the wavelets. Each wavelet has a list of participants and the servers of that waves will store their waves. With this point, a wavelet that you are not participant, you will not have access at this data, neither your server. You can be sure that your data is not shared with third party companies.
The architecture of wave servers are based on 2 key elements. The first one is the wave store is part of the server where wavelet’s operations are stored. The second element is the wave server, this part will resolve the operations to perform. This operations will make reads and writes of the waves on the store, just like in a normal server. But the intention of Federation is that other participants of waves can share waves with other wave providers. To achieve this, there are 2 more components: Federation Gateway and Federation Proxy.
Federation gateway is in charge of comunicate operation wavelets with local wavelets. Operate with new wavelets, process operations and much more, we will talk more about that in next posts. Federation proxy is in charge to comunicate wavelets with remote gateways.
This is a global vision of the Federation concept. There is much more to talk, but this is the base of Wave Servers Federation. Sooner we will expand all the parts of this protocol, so, please, stay tuned!
This website uses IntenseDebate comments, but they are not currently loaded because either your browser doesn't support JavaScript, or they didn't load fast enough.
Wave Federation
In this post we will introduce the Federation concept.
Federation is the protocol used for the servers to be able to connect their own users with other servers. The Federation lets Wave be a decentralized platform, or in other words, anyone has the chance to create his own servers. This servers will share waves between them. This will allow different networks to share the data that the users choose, fast and on real time.
A wave is nothing but an envelope that among other information stores wavelets. A wavelet can store documents, pictures, and any kind of data. The copies of the wavelets are shared between the wave servers that has at least one participant. One of this server will be the hosting server of the wave.
With this definition of ‘wave’ we can see that a wave is not an indivisible element, a wave is a set of elements called wavelets. When a user wants to open a wave, he recieves a view of the wavelets that he is participant. This makes that each user might have a different view of the same wave. With this feature we can make easily private messages restricting the users that can have access to the wavelet. Some documents represent rich text messages in the wavelet, these are called “blips”.
To identify them, each wave has an unique identifier and domain. The domain is the server domain.
As we know, waves are stored in different servers. But what the servers really share are the wavelets. Each wavelet has a list of participants and the servers of that waves will store their waves. With this point, a wavelet that you are not participant, you will not have access at this data, neither your server. You can be sure that your data is not shared with third party companies.
The architecture of wave servers are based on 2 key elements. The first one is the wave store is part of the server where wavelet’s operations are stored. The second element is the wave server, this part will resolve the operations to perform. This operations will make reads and writes of the waves on the store, just like in a normal server. But the intention of Federation is that other participants of waves can share waves with other wave providers. To achieve this, there are 2 more components: Federation Gateway and Federation Proxy.
Federation gateway is in charge of comunicate operation wavelets with local wavelets. Operate with new wavelets, process operations and much more, we will talk more about that in next posts. Federation proxy is in charge to comunicate wavelets with remote gateways.
This is a global vision of the Federation concept. There is much more to talk, but this is the base of Wave Servers Federation. Sooner we will expand all the parts of this protocol, so, please, stay tuned!
Etiquetas:Google Wave, Wave Federation, wave server
If you like what you see, please, support us:
Posts that may be of your interest: