Indigo and .NET's Context Architecture Part 2

Following on from my previous post about Indigo and .NET's context architecture, it seems we may have the answer as to how a rich services framework (Indigo?) is going to be made easily accessible to users... call context...

“Object context is affiliated with a specific object (or set of objects) independent of which methods are executing on that object.

Call context is affiliated with a logical control flow independent of which objects may be involved in the flow.

In Indigo, we're orienting more on call context than object context - it's simpler for developers to grok as well as more amenable to the service-oriented design style.“

Don Box