OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] Interesting XML-DIST-APP thread

[ Lists Home | Date Index | Thread Index ]

1/10/2002 8:59:50 AM, Francis Norton <francis@redrice.com> wrote:

>Roger L. Costello wrote:
> >
> >  Are you saying that Web services
> > will push more of the processing onto the client, 

>Just speaking for myself, surely that's axiomatic? 

Maybe I don't follow, but this can't be "axiomatic" when one prominent
use case for Web Services is to allow books to be ordered, 
schedules to be checked, etc. from very light wireless devices.

>Web Services won't suport an advertising model,

Again unless I'm misunderstanding, this appears to equate
"Web Services" with RPC using XML and HTTP.  Several of the posters
in the xml-dist-app thread made the point that XML, HTTP, and SOAP (etc.)
can be used to support alternative, asychronous communications
and server-based coordination models.  Consider a system that allowed 
suppliers to "advertise" available seats or rooms or books in a database
or "XML space" via SOAP interfaces, and allowed consumers to 
request specific seats or rooms or books via another SOAP interface that
generated a query to the shared DB or space.  That  would be a "web service," 
albeit one that uses a richer server-side coordination model rather than a 
simple "check every source via RPC and let the client sort it out" coordination model.
Likewise, a SOAP interface that lets one use a cellphone to launch an "agent" 
that would run on a server, query multiple databases or websites for the
best price on a specific seat/room/book, then e-mail  back its recommendation,
is still a "web service" to me.  Sorry if I'm belaboring an obvious point ...

[ordering books, checking schedules, checking stocks]

>All these can get a better user interface from the client side - indeed, 
>they'll probably spawn the next generation of desktop applications, and 
>will be way more efficient as web services than as browser queries.

On the other hand, I fully agree that the most realistic short-term use for
SOAP/UDDI/WSDL is simply to do cleanly and interoperably with XML
what is now done with all sorts of HTML and HTTP voodoo, hand-coding,
and fragmentary documentation.  When you have a fat client, exploit it!


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS