RE: wsa:Action in responses

The tricky bit here is that even in a world of "EPRs everywhere", you
still need some context information in order to know what to do with
them in order to successfully achieve some purpose.  Typically this
means at least some kind of description of the service structure (WSDL),
semantics (HTML docs or a phone call), and perhaps also conversation
state (sessions, etc).  You could easily imagine embedding this info
(which would include which message to send next, including perhaps an
action value) into an EPR, in order to do a simple form of process flow,
but we'd use extensibility in order to achieve that rather than baking
it in to the core specs.

--Glen 

> -----Original Message-----
> From: public-ws-addressing-request@w3.org 
> [mailto:public-ws-addressing-request@w3.org] On Behalf Of 
> Conor P. Cahill
> Sent: Tuesday, March 15, 2005 8:38 AM
> To: Hugo Haas
> Cc: WS-Addressing
> Subject: Re: wsa:Action in responses
> 
> 
> 
> 
> Hugo Haas wrote on 3/15/2005, 8:27 AM:
> 
>  > Actually, I see [action] associated with a message, not 
> any particular
>  > sending or receiving node: as the spec describes it, it is "an
>  > identifier that uniquely (and opaquely) identifies the semantics
>  > implied by this message."
> 
> So I was smoking some rope.   I was looking at this element as being
> used in our dispatching layer for application callbacks, which
> works fine on an incoming request, but doesn't always work for
> responses.
> 
> Conor
> 
> 
> 
>

Received on Tuesday, 15 March 2005 21:22:04 UTC