W3C home > Mailing lists > Public > www-tag@w3.org > July 2003

RE: Proposed issue; Visibility of Web services

From: Bullard, Claude L (Len) <clbullar@ingr.com>
Date: Wed, 16 Jul 2003 16:16:20 -0500
Message-ID: <15725CF6AFE2F34DB8A5B4770B7334EE022DC5B0@hq1.pcmail.ingr.com>
To: "'Mike Champion'" <mike.champion@softwareag-usa.com>, www-tag@w3.org

I for one will be interested in seeing given the XMSF group 
work if RPC or REST have to be preferred for distributed 
simulation, or if some combination will work, or if Web 
Services a la SOAP work at all for real time and near 
real time systems.  We know XML works because we have 
existence proofs in the form of X3D browsers.  But 
the communications backbone issues are far from clear 
at this time, IMO.  For that reason, one must always be 
able to make those tradeoffs for specific scenarios 
and it may be the case that the scale, intranet to internet, 
is not the only criterion.  We tend to buy into the coarsely 
grained loosely coupled scenario uncritically without regard 
to the behavioral and fidelity characteristics of the content.

len


From: Mike Champion [mailto:mike.champion@softwareag-usa.com]

Solutions lie on a 
continuum from a pure REST architectural style to a pure RPC/distributed 
object architectural style. One objective of the WSA is to help architects 
and specwriters better understand the tradeoffs for specific scenarios.  
For example, XML Document exchange over HTTP (e.g. whatever "son of RSS" is 
called today -- http://intertwingly.net/wiki/pie/)  is probably a case for 
which a RESTful approach is close to optimal.  But RPC can make lots of 
sense in well-managed, homogenous intranet envrionments where the necessary 
tight coupling is not a practical problem.
Received on Wednesday, 16 July 2003 17:16:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:55:59 UTC