The Session Component
A good analogy for a Session is a meeting, to which the "participant" Web services are invited. In order to participate in the meeting you have to join the conversation. The most important rule is that all messages should be sent through Session, so that the Web service participants do not need to be aware of each other.
In an application that consists of Web services, all "application" Web service calls should be sent through the Connected Services Framework Session component so that no Web service directly calls any other Web service. This enforced separation means that each Web service is modular and that applications can be constructed, deployed, and upgraded faster than if the Web services had dependencies between them.
Participants can be either WSE Web services or regular Web services. They can be .NET-based .ASMX Web services or Web services that use popular non-Microsoft technologies.
The Session component consists of three endpoints: SessionAdminManager, SessionManager and Session.