Bron: Microsoft Watch
Indigo: The 'Other' Programming Framework
We've been writing about Indigo for two years now, without knowing exactly what it is. But finally, we're getting some clarity on Microsoft's "other" programming framework, which will reside alongside the .Net Framework (version 2) deep inside Longhorn.
One of the key Indigo team members - XML Messaging architect Don Box - refers to Indigo as "a state of mind." Actually, it seems a tad more concrete than that, based on some of the new conference-session info available via the PDC schedule.
Indigo Info Leaks in 2001
Box: Indigo On My Mind
Indigo Sessions at PDC
Here is the latest working definition of Indigo, according to Microsoft: "'Indigo' is Microsoft's programming model and framework for building connected applications and Web services. Indigo brings together the best of .NET Remoting, MSMQ, ASMX and .NET Enterprise Services to form a unified model and runtime for building connected applications on the Windows platform."
Translation: .Net Remoting is a framework for transporting messages to and from remote locations. MSMQ is Microsoft message queuing. ASMX has to do with XML Web services created within managed code. .Net Enterprise Services is the new and improved name for COM+.
More on .Net Remoting
Check Out "Using .Net Enterprise Services to Build Distributed Apps"
Indigo will be built into Longhorn, and maybe even some Indigo-savvy applications. I wouldn't be surprised to see it embedded in the Yukon version of the SQL Server database, for starters.
Some company watchers have mistakenly labeled Indigo as version 2 of the .Net Framework. An honest mistake ... and one we ourselves nearly made. But Indigo is a different beast all together. It builds on top of the Web Services protocols (which Microsoft hopes will some day become the underpinnings of the Net, "much like TCP and HTTP powered the Web we have today," according to another Indigo session description). The Web services protocols upon which Indigo builds: WS-Security, WS-Transaction, WS-Reliable Messaging, WS-Addressing and WS-Policy.
Up until about a year ago, it was possible to find references all over Microsoft's Web sites to its .Net frameworks - plural. We asked again and again what constituted a ".Net framework," other than THE .Net Framework we all know and love. We were told there was one and only one .Net Framework: The one comprised of the Common Language Runtime, base framework classes, Active Server Pages .Net, Windows Forms, et. al.
A Refresher: What Is THE .Net Framework?
Now the real picture looks a little clearer. There *are* multiple programming frameworks that rely on .Net. Indigo is one. Net Remoting is another. Wonder if Avalon counts as yet another? ....Guess we'll see at the PDC.