W3C home > Mailing lists > Public > www-ws-arch@w3.org > June 2002

Re: Aims and Objectives

From: Mark Baker <distobj@acm.org>
Date: Thu, 20 Jun 2002 10:38:47 -0400
To: Mark Hapner <mark.hapner@sun.com>
Cc: www-ws-arch@w3.org
Message-ID: <20020620103847.O17419@www.markbaker.ca>

Hi Mark,

On Tue, Jun 18, 2002 at 10:16:02PM -0700, Mark Hapner wrote:
> 
> Francis,
> 
> You use the terms event, notification, and message to refer to forms of one way
> communication between producers and consumers. Are these just different uses for
> messaging or are they different service models?
> 
> It is clear that 'volunteering' as used here is meant to capture some special
> form of producer consumer interaction that goes beyond messaging and RPC. Is it
> some form of publish/subscribe paradigm?

I have similar concerns.  Rather than listing off an undoubtedly
incomplete list of message exchange patterns, could we just say that the
architecture should support as many as possible, or something to that
effect?

> A basic element of composition on the web is a resource. Is composition of web
> service resources covered in your composition goal? 
> 
> Given the current design of Soap 1.2, I don't believe it is possible for the
> response of one service to be be constructed as a service request/message so it
> is not clear how to create a pipe like composition of services without writing
> code. Is this an example of what you mean by service composition?

SOAP 1.2 supports this, but it's up to the developer to use it this way.
Without generic semantics, I agree, composition does require new code.
When we sketch out the architecture diagram, and identify our components
and interactions, this should become evident.

MB
-- 
Mark Baker, CTO, Idokorro Mobile (formerly Planetfred)
Ottawa, Ontario, CANADA.               distobj@acm.org
http://www.markbaker.ca        http://www.idokorro.com
Received on Thursday, 20 June 2002 10:28:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:00 GMT