[
Lists Home |
Date Index |
Thread Index
]
Further down is better stuff:
"Loose coupling is central to the nature of Web services-based application integration. That's why it seems to me that the right model for XML in Web services is a message-oriented, document-based one rather than one based on remote procedure calls."
Strong encapsulation, negotiate exchange types for a duration (document types change
too), trust but validate, never ever ever let the marketing people into the
process until after the schemas are done.
len
-----Original Message-----
From: Mike Champion [mailto:mc@xegesis.org]
4/11/2002 10:59:48 AM, "Simon St.Laurent" <simonstl@simonstl.com> wrote:
I agree, that's a very thought-provoking piece. Another article I just noticed
yesterday is also well worth careful thought: Adam Bosworth on loosely coupled
architectures for web services.
http://www.fawcette.com/xmlmag/2002_04/magazine/departments/endtag/
"The only real success story to date in the world of loose coupling is the Web
itself. ... The only thing the browser knows is the wire format (usually HTML) and
the protocol."
-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>
The list archives are at http://lists.xml.org/archives/xml-dev/
To subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl>
|
