OK Ray, I'll Bite…. One of my biggest complaints about Groove has been its closed architecture. Once you get in the “Groove,” it is hard to get in or out to any other arcthitecture. Some of that closed mentality changed today.

Today Groove announced

OK Ray, I'll Bite…. One of my biggest complaints about Groove has been its closed architecture. Once you get in the “Groove,” it is hard to get in or out to any other arcthitecture. Some of that closed mentality changed today.

Today Groove announced it was going to allow Groove users to exchange instant messages with .Net Messenger users. This means that Groove has a gateway to .Net Messenger or supports the protocol natively. It also means that Groove has done some integration with the .Net Messenger name space. This marks the first step to some interoperability from Groove.

Ray, (that's Ray Ozzie) if you really want to pull this off, give us a SOAP or XML-RPC interface in and out of Groove. If there's one thing you might remember from Notes: monolithic architectures suck.

Shifting from a client-server architecture to a network architecture with Groove is one thing, interoperability is another. Show us your stuff!

Also, tell us how you integrated with .Net Messenger. If you really want to give us some IM integration, how about supporting native Jabber? I am sure Jeremie Miller would be happy to work with you on that. [Craig Burton: logs, links, life, and lexicon]

Leave a comment