RE: WS-Addr issues

Paul

[should have replied to all, appologies]
 
> my electricity bill is sent to "accounts department", "Southern Gas*, 
> London" accounts department" being the action in this case.

Ok - that's a very enlightened view of an action.
 
> endpoints are about /routing/ and action is about /dispatching/ i 
> don't see how the ws-addressing spec could specify that dispatch 
> contents must be, say a noun rather than a verb.

Endpoints are addressable, and actions are something to do 
with some activity beyond the enpdoint. Therefore I fail to 
see how ws-addressing should busy itself worring about 
dispatching which to my mind is out of scope.
 
> So whilst i'm happy for *your* implementations to process 
the service 
> specific message contents to work out the action to be 
taken, removing 
> action will preclude other styles of service from using 
ws-addressing, 
> in particular endpoints using a generic security or routing 
proxy (the 
> post room in the gas board example).

It will preclude those services which need additional out of 
band information to enable dispatch. Those services which 
have poorly designed message exchanges.
 
So perhaps I will moderate my position to make wsa:action 
optional so that services which have to be badly designed 
(perhaps there are some legacy reasons why this is so) can 
insert an action to help the service dispatch. Clearly there 
are options (which you point out) where dispatch via action 
is necessary, whereas there are cases (which I maintain) 
where dispatch via action is not neeeded.

I leave aside for the moment whether or not it is sensible to 
factor actions into addresses...

> (yes, i'm able to get my electricity from the gas company!)

That's not unusual. When I lived in the UK, my block of flats 
was electricity only and the supplier was British Gas.

Jim

Received on Friday, 5 November 2004 15:09:39 UTC