[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ws-caf] WS-Resource Framework
|
The specs and presentations can be found at: BTW… they are trying hard to
persuade people here at GlobusWORLD that the use of WS-Addressing to identify a
“stateful resource” (a resource whose state can be represented as
an XML document) is not the same as the use of context in the case of
WS-AtomicTransaction. Personally, I can’t see the difference. They are
both ways to do message correlation and achieve stateful interactions. The
difference I see is that WS-Resource is a way to reason about distributed objects. Now, whether people are going to start
building loosely-coupled, large-scale applications around the concept of a
stateful resource with a coupled identity (WS-Address + local identifier) and a
coupled interface (the interface of the Web Service identified by the first
part of the WS-Address) that will have to be decided. Personally, I think it
still looks like distributed objects but the IBM folks over here assure me that
they are not doing objects and are truly service-oriented. People here may
disagree with me. I guess only time will tell whether this approach has any
benefits. In their presentations, they are making
the following distinctions (I am not going to comment for now… I’ll
leave this up to you): - “A truly stateless service”
(the set of operations that identify a Web service) - “A conversational service” - “A stateless service that acts upon
stateful resources” Best regards, -- From:
Jean-Jacques Dubray [mailto:jeanjadu@Attachmate.com] Yet another context management specification from IBM
et al: http://www.marketwire.com/mw/release_html_b1?release_id=61977 JJ- |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]