BT

WS-Context becomes an OASIS standard

| by Mark Little Follow 12 Followers on Apr 11, 2007. Estimated reading time: 1 minute |
The OASIS WS-Context specification has been approved as an OASIS standard, with no votes against it. The committee has been working on WS-Context under the WS-CAF umbrella of specifications, which also includes the WS-CoordinationFramework and WS-TransactionManagement specifications. Although WS-Context is unique in what it defines, there is overlap with the latter two specifications and what is going on in the WS-TX committee, which is backed by IBM and Microsoft (and started years after WS-CAF). Therefore, it is unlikely that any other standards will come out of the WS-CAF group.

There has been a lot said about WS-Context over the years, most recently at the W3C workshop on Web of Services and in the majority it has drawn positive comments. In summary, WS-Context defines a basic (extensible) context structure that can be associated with an abstract activity: the lifetime of the activity is the lifetime of the context. The activity can then be used to model a session: all interactions on a session-oriented service in the scope of an activity will be uniquely and unambiguously tied to that activity through the context. Importantly, the context (and hence session) is not tied to the endpoint reference of the service: the same service can be addressed by multiple clients or services in the scope of different sessions concurrently. The session concept is therefore loosely coupled with respect to communication channels and service endpoints: the session may be used in conjunction with a service for a short period or even shared across multiple services. Late binding also means that protocols may use WS-Context to support either ephemeral or long-lived sessions associated with a fixed service endpoint definition as appropriate within an application.

Although there may appear to be overlaps with WS-Addressing, the two are more complimentary than competitive. Think of the possible relationship like URIs and cookies in the traditional Web. If used together and used right, loosely coupled, scalable stateful and stateless interactions in Web Services are possible. If used incorrectly, or ignored then closely coupled, brittle systems can result. Whether WS-Context has a big impact on the evolving Web Services architecture remains to be seen. The fact that IBM and Microsoft were not involved will certainly hinder the take-up and influence.

Rate this Article

Adoption Stage
Style

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Discuss

Login to InfoQ to interact with what matters most to you.


Recover your password...

Follow

Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.

Like

More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.

Notifications

Stay up-to-date

Set up your notifications and don't miss out on content that matters to you

BT