Re: message exchange patterns and # of parties

There is no convenient one-word summary of all the different roles that
can be played by
nodes-that-are-not-in-the-role-of-service-but-are-participating-in-an-e
xchange.  client, consumer, subscriber, and peer are all appropriate, at
times.  service (or peer service) is sometimes appropriate. 
"participant" is inclusive, but happens to include the service.  I like
"partner"; other people hate it.  *shrug*

Amy!
On Fri, 12 Sep 2003 15:33:06 -0400
David Booth <dbooth@w3.org> wrote:

> At 12:49 PM 9/12/2003 -0400, Amelia A. Lewis wrote:
> >On Fri, 12 Sep 2003 12:32:16 -0400
> >David Booth <dbooth@w3.org> wrote:
> >
> > > On yesterday's WS Arch WG call, the WG confirmed agreement on the
> > > following terminology for the parties involved in an interaction:
> > >
> > >          Terms to Avoid          Terms to Use Instead
> > >          ==============          ====================
> > >          client, consumer        requester
> > >          server                  Web service, service or provider
> > >
> > > Maybe we should follow the WSA WG's lead in our documents as well?
> >
> >Since a subscriber is *not* a requester, nor is the second
> >participating node in any output-first operation, I would prefer to
> >avoid making these mistakes, even if they can be justified by
> >pointing out that WSA made them first.
> 
> That was pointed out during discussions in the WSA WG, but we didn't
> have any better ideas that got any traction.
> 
> 
> -- 
> David Booth
> W3C Fellow / Hewlett-Packard
> Telephone: +1.617.253.1273
> 
> 


-- 
Amelia A. Lewis
Architect, TIBCO/Extensibility, Inc.
alewis@tibco.com

Received on Friday, 12 September 2003 15:55:54 UTC