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

RE: S600: Comments on the Web Services Architecture Usage Scenari o s document (was Re: New draft of the Web Services Architecture Usage S cen arios document)

From: Damodaran, Suresh <Suresh_Damodaran@stercomm.com>
Date: Fri, 21 Jun 2002 10:19:50 -0500
Message-ID: <40AC2C8FB855D411AE0200D0B7458B2B07C5974F@scidalmsg01.csg.stercomm.com>
To: "'Mark Baker'" <distobj@acm.org>
Cc: "'Hugo Haas'" <hugo@w3.org>, www-ws-arch@w3.org

Hi Mark,

You really got me here, I thought I put a smiley at the end:-)
I am not quite ready to talk about it in detail.

Well, here are some uncooked general thoughts on "address based" discovery 
(along the lines of "Zero protocol"):
	1. Given a URL, make it possible to discover other URLs, i.e.,
		Support URL1 -> URL2, URL3, ..., where
		 -> is a mapping defined and implemented for the purpose of
reliability, or for identifying the right URL for the accessor, etc. You
might say, apart from HTTP none of the other protocols define any such
mapping. Well, just give some time, then.
	2. The URL is an access point, and now go over to the higher layer:
Service layer.
	(I know you have some philosophical differences here, but let us not
get lost in weeds)
	Given a service description, provide a mapping from a service
description to one or more service implementations 	
	- here is where SOAP based discovery comes in picture for
reliability, finding the right 	actions are available, etc. Essentially a
"service reflection mechanism" and ways to 	describe and communicate it.

Sterling Commerce   

-----Original Message-----
From: Mark Baker [mailto:distobj@acm.org]
Sent: Friday, June 21, 2002 10:06 AM
To: Damodaran, Suresh
Cc: 'Hugo Haas'; www-ws-arch@w3.org
Subject: Re: S600: Comments on the Web Services Architecture Usage
Scenario s document (was Re: New draft of the Web Services Architecture
Usage Scen arios document)

Hi Suresh,

On Fri, Jun 21, 2002 at 09:10:43AM -0500, Damodaran, Suresh wrote:
> As you know, URL, as defined in [1], includes other protocols apart from
> http.
> Though HTTP GET may be listed as a "candidate technology," as you suggest,
> my preference is
> not to limit ourselves to HTTP. An application may want to use ftp based
> service discovery,
> or smtp based. Or, a SOAP based service discovery (assuming whatever
> underlying protocols). 
> Just leave the door open for discovery:-)

What do you mean by "discovery" in this context?  I know what HTTP based
discovery is; you just discover a URI.  But what is FTP based service
discovery, for example?  As far as I know, FTP has no notion of it.

(I won't even hazard a guess at what SOAP based discovery is 8-)

Mark Baker, CTO, Idokorro Mobile (formerly Planetfred)
Ottawa, Ontario, CANADA.               distobj@acm.org
http://www.markbaker.ca        http://www.idokorro.com
Received on Friday, 21 June 2002 11:20:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:05:34 UTC