- From: Mahan Michael (NRC/Boston) <michael.mahan@nokia.com>
- Date: Tue, 10 Dec 2002 13:29:07 -0500
- To: "ext Newcomer, Eric" <Eric.Newcomer@iona.com>, "Baker, Mark" <distobj@acm.org>
- Cc: David Orchard <dorchard@bea.com>, <www-ws-arch@w3.org>
Hi Eric, On 12/9/02 12:36 AM, "ext Newcomer, Eric" <Eric.Newcomer@iona.com> wrote: > > <mark:messageid>http://foofoo.org/mid/232394820480234</mark:messageid> > <mark:qos>http://ackack.org/qos/ack</mark:qos> > > But I'd simplify it further to just send a plain "ack" for a message with a > given unique ID. In that context the rest of the "qos" namespace URI would not > really be needed but I agree with your idea or assumption that whatever we do > should be extensible and flexible. But actually a simple ack is what I'd like > us to focus on for the initial proposal, so perhaps an even simpler example > would be better: > > <mark:ack>http://ackack.org/ack</mark:ack> > While agreeing that this is simplier, isn't reliability a qos feature and should/could be grounded or encapsulated as such? Mike Mahan, Nokia
Received on Tuesday, 10 December 2002 13:39:23 UTC