Google Wave Backstage 132
As Google Wave is about to be released to 100,000 beta testers tomorrow, reader snitch writes in with a link to an in-depth interview with Dhanji Prasanna, whose title is Core Engineer. It covers some of the technologies, tools, and best practices used in building Wave. "InfoQ: Would you like to give us a short technical outline of what happens to a message (blip) from the moment a user types it in the web client, until becomes available to every one else that is participating in that wave — humans or robots? ... Dhanji: Sure, a message written in the client is transformed into a series of operations that are sent to the server in real time. After authenticating and finding the appropriate user session, the ops are routed to the hosted conversation. Here these ops are transformed and applied against other incoming op streams from other users. The hosted conversation then broadcasts the valid set of changes back to other users, and to any listening robots. This includes special robots like the ones that handle spell checking, and one that handles livesearch (seen in the center search-panel), as well as explicit robotic participants that people have developed. Robotic participants write their changes in response to a user's and these are similarly converted into ops, applied and re-broadcast."
Re:Sounds like Bullshit (Score:3, Informative)
Re:Where is the CLI version? (Score:2, Informative)
I know it is all supposed to be open source and everything but there is no Client-server protocol because it is assumed to be a web application so for a long time all we will have is Google's bloated JavaShit-filled and presumably ad-laden perpetual beta web interface.
uh... http://www.waveprotocol.org/ [waveprotocol.org]
PyGoWave (Score:3, Informative)
If you're itching to try out Google Wave like I am, a bunch of developers have already launched their own wave server implementation. A combination of Python + Django Framework + Javascript. You can create an account and have a play around, or you can download and run your own. Note that its still in early alpha state.
http://pygowave.net/ [pygowave.net]
Re:Where is the CLI version? (Score:3, Informative)
won't work, because you actually need to be a server (i.e. you need a domain with SRV records and open ports and a reasonably static IP and whatnot).
The open client protocol problem is simply a problem that hasn't been solved yet. I'm sure a solution will arrive. As long as the server-to-server federation protocol is open, you're golden.
Re:Cautiously Optimistic (Score:5, Informative)
One of the most important difference b/w how Exchange and Wave work is that the later is hosted by Google and hence controlled by it.
The protocol is open and Google has publicly stated anyone is free to host their own server. So we can safely toss that concern right out.
With Wave we would all have to trust google with our data, which a lot of companies in the world may not be willing to do.
Nothing could be farther from the truth. The truth is, Wave is built from the ground up to concurrently integrate, in real time, both open (Google or 3rd Party) and closed (company x's own ) Wave servers in a transparent manner. With wave, you have to trust no one other than your self. Period. In fact, that is so much so the literal truth, you are less dependent on another company for your own technological collaborative destiny; which is absolutely not true for Exchange.
Wave understands locality and security so its possible to security integrate public Wave services with private Wave servers and services without ever sharing data outside your own company.
In short, nothing you've offered as fact is even remotely true.