October 28, 2003
@ 05:36 AM
Comments [3]
Indigo

Clemens Vasters writes

Indigo is the successor technology and the consolidation of DCOM, COM+, Enterprise Services, Remoting, ASP.NET Web Services (ASMX), WSE, and the Microsoft Message Queue. It provides services for building distributed systems all the way from simplistic cross-appdomain message passing and ORPC to cross-platform, cross-organization, vastly distributed, service-oriented architectures providing reliable, secure, transactional, scalable and fast, online or offline, synchronous and asynchronous XML messaging.

I think is truly awesome, they (folks like Don Box, Doug Purdy, Steve Swartz, Scott Gellock, Omri Gazitt , Mike Vernal , John Lambert et al) have not just cooked up a brand new distributed computing platform but have built it on open standards and open technologies meaning that probably for the first time in decades there won't be artifical, politics induced divisions limiting a distributed computing technology to particular platforms or operating systems (i.e. like CORBA, DCOM & Java RMI). The extra goodness is that these open standards are all XML based so crazy XML geeks like me can do stuff like this or people like Sam Ruby can do stuff like that.

The next generation of DCOM, just that this time it interoperates with everyone regardless of what programming language or operating system they are running.

Fucking sweet.


 

Categories: Life in the B0rg Cube | XML

« Answers To Some Questions About XML in W... | Home | What Exactly Can RSS Bandit Do?  »
Tuesday, 28 October 2003 17:27:52 (GMT Standard Time, UTC+00:00)
It would be great if the specs were open, but as of right now, the ratio of proprietary WS-xxx specs to open standards efforts is about 15:1. Hope that changes very soon, but until it does, it's just MSFT/IBM private. :(
Rich salz
Wednesday, 29 October 2003 07:44:45 (GMT Standard Time, UTC+00:00)
Rich,

We're trying to get the protocol stack to work and to get broad adoption in real products.

While you may not like the way we're going about it, be clear that we're not looking to turn the WS-* stack into a product - unless I'm mistaken BillG said publicly that it's all RF - may a thousand flowers bloom...

DB
Don Box
Thursday, 30 October 2003 00:29:03 (GMT Standard Time, UTC+00:00)
Rich, we have a process whereby these specifications get into standards bodies. We believe that it's very important to vet implementation with our parnters in order to end up with a specification that's implementatble before we submit. The workshop process is designed specifically for this purpose. When we've done enough technical work to prove the technical merit of the spec, through implementation, then turning it over to a standards body makes sense to use. To a certain degree, we feel it's a more efficient way to get the specs out to standards bodies.
Scot Gellock
Comments are closed.