W3C home > Mailing lists > Public > public-ws-async-tf@w3.org > May 2005

RE: Asynch scenarios

From: David Orchard <dorchard@bea.com>
Date: Fri, 6 May 2005 11:40:16 -0700
Message-ID: <32D5845A745BFB429CBDBADA57CD41AF0F75B1C5@ussjex01.amer.bea.com>
To: <Marc.Hadley@Sun.COM>
Cc: <public-ws-async-tf@w3.org>

Ok, I'll do all of those.  I was originally trying to keep the fragments
an extract of the test cases.  But I'm glad to replace all the
microsoft.com names with bea.com names :-)  Or perhaps I could use some
of the actual examples from the specs....

Dave

> -----Original Message-----
> From: Marc.Hadley@Sun.COM [mailto:Marc.Hadley@Sun.COM]
> Sent: Friday, May 06, 2005 9:03 AM
> To: David Orchard
> Cc: public-ws-async-tf@w3.org
> Subject: Re: Asynch scenarios
> 
> Some comments:
> 
> (i) Given that [message id] and [relationship] are key for async use
of
> addressing, I think it would be useful to include them in the
fragments
> (they are much more pertinent to the discussion than e.g. [action] ).
> 
> (ii) Many (all ?) of the example use the same address for reply/fault
> to as the original to address, this could be confusing (why would I
> want to send faults to the address i'm sending a message to other than
> as a splendidly recursive DOS attack), suggest you make up a 'my fault
> sink' address to avoid confusion.
> 
> (iii) Don't use the anonymous URI from the submission, use the one
from
> the latest public draft.
> 
> (iv) s/reference properties/reference parameters/g
> 
> (v) Might be worth noting that you can s/FaultTo/ReplyTo/ in the
robust
> examples.
> 
> Marc.
> 
> On May 5, 2005, at 3:32 PM, David Orchard wrote:
> 
> > I've done almost all the edits that are critical: added readability
> > constructs like TOC, lines, description, WSDL 1.1 and WSDL 2.0
> > interface and binding fragments, and a dummy one-way protocol.
> >
> > I did not add any suggestions for WS-A extensions, nor show the soap
> > meps for WSDL meps, nor do the in-optional-out or out-only patterns.
> >
> > Please let me know whatever mistakes that I've made, and I'll
> > incorporate ASAP. You can send privately or to list, doesn't matter
to
> > me.
> >
> > Cheers,
> > Dave
> > <asynch-scenarios.html>
> ---
> Marc Hadley <marc.hadley at sun.com>
> Business Alliances, CTO Office, Sun Microsystems.
Received on Friday, 6 May 2005 18:40:25 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Friday, 6 May 2005 18:40:25 GMT