- From: Doug Davis <dug@us.ibm.com>
- Date: Tue, 14 Apr 2009 09:09:07 -0400
- To: public-ws-resource-access@w3.org
- Message-ID: <OFEB4E0DEE.5CF88B9E-ON85257598.0047D650-85257598.00483F89@us.ibm.com>
I wouldn't describe the situation the same way. I don't believe the
proposal suggests that
people keep 'A' - rather it simply offers it as an option for those who do
not wish to change
their code. If I were starting from scratch with my implementation I
would much prefer to
have a single way of expressing how/where to send messages, not two.
That's the
more interoperable solution.
As for "keeping A" - let's not forget that "A" is broken. People are free
to continue to use it
as they do today, as long as they understand the limitations. But WS-E
itself should promote
a solution that isn't broken and is consistent with the rest of the WS-*
stack.
thanks
-Doug
______________________________________________________
STSM | Standards Architect | IBM Software Group
(919) 254-6905 | IBM 444-6905 | dug@us.ibm.com
The more I'm around some people, the more I like my dog.
Yves Lafon <ylafon@w3.org>
Sent by: public-ws-resource-access-request@w3.org
04/14/2009 05:44 AM
To
Doug Davis/Raleigh/IBM@IBMUS
cc
public-ws-resource-access@w3.org
Subject
Re: [issue 6432] - a modest proposal
On Fri, 10 Apr 2009, Doug Davis wrote:
> Yves,
> Actually, what you describe is what we have now. We have two different
> ways of
> expressing how/where to send a message(s) within the same spec. We're
> moving
> towards one way. And, in doing so we're moving towards having it be
> consistent with
> all other WS-* specs. Code reuse! No specialized "message sending"
code
> needed
> just for WS-Eventing. That's even better for interoperability.
I am not talking about the quality of the solutions here. My point was
that we currently have solution 'A' in Eventing, and the possibility of
using solution 'B' using a mU trick. You propose to add in Eventing
solution 'B' but keep 'A' and just add a mU to 'A'.
Regardless of what are 'A' and 'B', I see absolutely no gain wrt
interoperability. We still have two different solutions that won't
interoperate.
--
Baroula que barouleras, au tiéu toujou t'entourneras.
~~Yves
Received on Tuesday, 14 April 2009 13:09:53 UTC