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

RE: what is discovery - One concrete proposal

From: Ugo Corda <UCorda@SeeBeyond.com>
Date: Fri, 11 Oct 2002 10:37:29 -0700
Message-ID: <C513FB68F8200244B570543EF3FC65370A855BA1@MAIL1.stc.com>
To: "'Ricky Ho'" <riho@cisco.com>
Cc: www-ws-arch@w3.org

That's cheating :-)

Ugo

-----Original Message-----
From: Ricky Ho [mailto:riho@cisco.com]
Sent: Friday, October 11, 2002 10:02 AM
To: Ugo Corda; 'Heather Kreger'
Cc: www-ws-arch@w3.org
Subject: RE: what is discovery - One concrete proposal


Imagine the client application to be a web services browser that allows a 
*human* to lookup what web service is available, pick one and invoke 
it.  The naming convention, verbs .. etc is up to the human user to
interprete.

Ricky

At 09:01 AM 10/11/2002 -0700, Ugo Corda wrote:

> >2. The client discovers the interface specifics and the service instance
> >during runtime. In the deployments of this that I know of, they use a DII
> >style interface, like the JAXRPC call object or the WSIF apis to figure
out
> >what message to create, create it and process the results.  There are not
> >many of these out there.
>
>I am not surprised that there are not many of those out there. What
>surprises me is that there are any at all. How does a client application
>figures out the semantics of an interface it has never encountered before?
>It has to be something about very well delimited domains and very well
>defined naming conventions for verbs and parameters (or very familiar
>namespaces) ...
>
>Ugo
Received on Friday, 11 October 2002 13:38:09 GMT

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