sent2null space

In a post from several months back I mentioned the Google "Wave" server technology that had been announced by many of the IT media shops. Google provided many tech. videos on the service on youtube and after watching a few of them I got the gist of the service as being basically an open source collaboration server for a more real time collaboration experience between users on the server. Shortly afterward I was asked by Juliette Powell what the main differences were between the numeroom.com service and google wave were. I explained some of the architectural differences based on what I knew of them at the time in this post which had some great input in the comments for that post but on the business end, numeroom.com collaboration provides a solution for small businesses that makes it more efficient than going with any server based system for several important reasons as indicated in the list below: No need to host the collaboration server and services yourself. This is a hu...

I was recently asked this question by Juliette Powell , and thought it would be the great subject for a detailed blog answer as provided below: From an architectural view , the differences lie in approach. Where as, Google is tacking on real time or near real time collaboration to their existing messaging infrastructure in the form of Google Wave; Numeroom ties a set of collaboration functions into a secure package that is useful to both individual users AND to businesses. I designed it noticing the trend in the proliferating collaboration options about 3 years ago. Web 2.0 technology (XmlHttpRequest object to the clued in) enabled real time experiences that matched previous stand alone software but enabled user interaction that wasn't possible using decentralized stand alone software. The emergence of platforms as the new buzzword and engine behind a given service gave rise to many collaboration options. Meebo, Userplane, Campfire, Parachat, MeGlobe, LivePerson , Provide Support....