W3C home > Mailing lists > Public > www-ws-arch@w3.org > February 2004

RE: REST wrap-up (was Re: Web Services Architecture Document

From: He, Hao <Hao.He@thomson.com.au>
Date: Sat, 7 Feb 2004 09:11:07 +1100
Message-ID: <686B9E7C8AA57A45AE8DDCC5A81596AB0922DFBE@sydthqems01.int.tisa.com.au>
To: "'Mark Baker '" <distobj@acm.org>, "'Cutler, Roger (RogerCutler) '" <RogerCutler@chevrontexaco.com>
Cc: "'www-ws-arch@w3.org '" <www-ws-arch@w3.org>
I agree.  A constrained interface is fundamental.  That is why I 
always claim it is an important architectural constraint for any SOA. 
Unfortuntely, this point has been washed down quite a bit in the final 
document.  I was told that it is just a best practise.


-----Original Message-----
From: Mark Baker
To: Cutler, Roger (RogerCutler)
Cc: www-ws-arch@w3.org
Sent: 2/7/2004 8:46 AM
Subject: Re: REST wrap-up (was Re: Web Services Architecture Document

Thanks Roger (and Mike), for those answers.  They were just what I was
looking for, again.  I apologize for not asking them in the first round
of questions, but it only occurred to me afterwards that they wouldn't
provide me all the information I needed to really understand where folks
were coming from.

I presume you won't mind if I don't turn this into a thread 8-), but
just for the record, as you summized, I'm not in the a) camp, as my
understanding of software architecture tells me that some architectural
styles are not suitable for some domains (like the Internet).  I'll just
briefly mention again, that if you study enough Internet scale systems
(email, Web, instant messaging, even the telephone network), you'll find
that they *ALL* have one thing in common; a constrained interface
derived from an application abstraction (respectively, an inbox, a
resource, a user, and a telephone line).  I don't believe that's a


Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca

Received on Friday, 6 February 2004 17:10:19 UTC

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