During the 1990s, when people began saying that the Web was the next wave of technology and would replace the client-server wave of the 1980s, some pedantic sorts took pains to explain that the Web was client-server, just in a new guise.
Google envisage a host of federated wave servers all hosting waves, in the same way that email is hosted on many different servers.
But also, we envision that enterprises or techies will run their own Wave servers, in their own server closets.
This document lives on the Wave server and has a corresponding set of actions that generated it's current state.
If you guys are colleagues in an enterprise running your own Wave server, you start a private reply within a larger Wave, that private reply will never leave your corporate network.
It's a very important feature of the protocol that if a set of colleagues within an enterprise runs a Wave server, that will stay just between them — that data will never leave their network.
At the start of the decade, when a new breed of software made it possible to make one piece of hardware act as if it were several servers, companies embarked on a wave of server consolidation.
Perhaps, given the possibilities of running your own Wave servers, we would have our own, internal server, perhaps in the cloud, over which we would have complete control.
For corporate users, I can imagine corporate wave servers, with only approved collaborators and robots allowed.
I can't work out if this is a sly comment about the wave of server-based computing, or it's just because they really wanted to ruin Tron for me.
But if you appreciate the first for what it is (a camp delight), tolerate the second (we repeatedly had to wave for our server) and do not order the third, you can have a lot of fun here.
