In-Depth

Indigo: The Longhorn Communications Layer

Indigo is the core for communication in the next generation of Windows, code-named Longhorn. This model of its architecture gives you a good sense of what to expect from it.

Indigo is the core for communication in the next generation of Windows, code-named Longhorn (see Figure 1). It builds on Microsoft's vision of service-oriented architecture, which itself relies on the Web Services Enhancements (WSE) 2.0 specification for the next generation of Web services. It might not be clear from the diagram, but Indigo supports both a Web service-based and a remoting-based approach to communication. This architecture—and its underlying technologies—is intended to supply a new level of security and power to service-based architecture.

The communication pillar also includes (1) collaboration, but that lies outside the Indigo model proper. The framework support for collaboration between programs and (2) people should offer significant opportunities to those who create the next generation of collaboration software.

One way to get a toehold into the complexity of Longhorn is to look for a feature you're particularly interested in. For example, you'll find (3) transactions embedded deeply in the base operating system (see the "Longhorn: The Base Operating System" object model), as well as in Indigo's systems services. Similarly, security support runs from the base operating system through the corresponding pillars, where appropriate.

The initial release of Longhorn is a client operating system, but the new Indigo features won't be too interesting if they are available only on client machines. They also need to be available on the server machines the clients interact with. To that end, Microsoft has also announced that key portions of the Indigo/WSE 2.0 specification will be available for Windows Server 2003. —Kathleen Dollard

About the Author

Kathleen is a consultant, author, trainer and speaker. She’s been a Microsoft MVP for 10 years and is an active member of the INETA Speaker’s Bureau where she receives high marks for her talks. She wrote "Code Generation in Microsoft .NET" (Apress) and often speaks at industry conferences and local user groups around the U.S. Kathleen is the founder and principal of GenDotNet and continues to research code generation and metadata as well as leveraging new technologies springing forth in .NET 3.5. Her passion is helping programmers be smarter in how they develop and consume the range of new technologies, but at the end of the day, she’s a coder writing applications just like you. Reach her at [email protected].

comments powered by Disqus

Featured

  • Microsoft Agent Framework Makeover: Claws, Loops and Harnesses

    Microsoft's newly released Agent Framework Harness packages the loops, planning, memory, context management and safety controls that developers previously had to assemble around AI models themselves.

  • Visual Studio 2026 Gives Copilot Built-In Skills -- and Makes Them Prove Their Worth

    Microsoft is moving Agent Skills beyond bring-your-own instructions by shipping expert-authored workflows with the IDE, while keeping them off by default until testing shows their benefits justify the additional token use.

  • Copilot AI Billing Shock Met with Meters, Caps and Token-Saving Tools

    GitHub is layering spending limits, expanded credit allowances and increasingly granular usage reporting onto Copilot, while Microsoft is reworking Visual Studio and VS Code to expose -- and reduce -- the cost of agentic development.

  • The AI-Powered Software Development Lifecycle

    René van Osnabrugge makes the case that AI's biggest opportunity in software development is not faster coding -- it's reducing the friction everywhere else in the SDLC.

Subscribe on YouTube