Follow Slashdot stories on Twitter


Forgot your password?
Google Java

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."
This discussion has been archived. No new comments can be posted.

Google Wave Backstage

Comments Filter:
  • by martas ( 1439879 ) on Tuesday September 29, 2009 @04:19PM (#29584995)
    ... is making waves.

    I'll let myself out.
  • by jcwayne ( 995747 ) on Tuesday September 29, 2009 @04:41PM (#29585253) Homepage

    Somebody needs a hug.

  • by Anonymous Coward on Tuesday September 29, 2009 @04:43PM (#29585273)

    I've been looking forward to google wave for some time, especially considering the new client/server bssed cloud paradigm that this entails. The fact that we can now communicate on a global basis while still maintaining the orthodox model of local fat client computing aligned with mobile services gets me hard. When you align this with a local, services-based vertical operation you can really understand how this can compete with global iterations of matrix-based local operators. In fact, as i write this, me penis is getting hard and i am forced to take short breaks from typing while i slowly rub it up and down. When we look at the phenomenon of Google wave, and of course, of The Google itself, we cannot fail to look both to the past, and the future, as I slowly insert a dildo in my anus and begin to slowly fuck myself while rubbing my cock against a printout of the google home page, hopefully, to ejcaculate upon it and thus acheive catharsis.

  • by D Ninja ( 825055 ) on Wednesday September 30, 2009 @12:21AM (#29589187)

    Google OS + Waves + commodity hardware. If anything, at least the next version of windows will be much less expensive.

    So, basically, you're saying we can (wait for it)...wave...goodbye to high Windows prices?

    Alright, alright. I'm letting myself out...

I've got a bad feeling about this.