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

RE: Myth of Loose coupling

From: Doug Kaye <doug@rds.com>
Date: Wed, 1 Oct 2003 00:26:51 -0700
To: "'David Orchard'" <dorchard@bea.com>, <www-ws-arch@w3.org>
Message-ID: <033301c387ed$6355c470$c9a8a8c0@rds.com>


I like your list of loose-coupling properties. May I suggest two others that
I don't think are covered by your list?

1. Data validation through published schema. (As opposed to "by convention"
[brittle] or as part of the service [too fine-grained and noisy].)

2. Delayed binding. (Just in general.)


Doug Kaye, CEO
RDS Strategies LLC
doug@rds.com, www.rds.com www.itconversations.com

> -----Original Message-----
> From: www-ws-arch-request@w3.org [mailto:www-ws-arch-request@w3.org]On
> Behalf Of David Orchard
> Sent: Friday, September 26, 2003 6:01 PM
> To: www-ws-arch@w3.org
> Subject: Myth of Loose coupling
> I'm posting a link as I was asked to before on the start of a
> discussion on loose coupling.
> http://lists.w3.org/Archives/Public/www-ws-arch/2003Jan/0115.html
> I will say that I have come to have a somewhat revised view on loose
> coupling.  I would say that loose coupling is a combination
> of properties:
> - extensibility, so that additional information can be added without
> breaking receivers
> - evolvable changes in the interface, so compatible changes
> can be made.
> - rapidity of changes in the interface
> - on the web, the generic interface constraint, means that
> applications
> (browsers/search engines) are not dependent upon each site's protocol.
> - asynchrony, so that senders and receivers are decoupled in time
> - stateless messaging, so that senders need fewer messages
> and hence less
> chance of communication errors
> - use of URIs for identifying resources.  This means that
> identifiers are
> very constrained and easily transferred.
> - No vendor specific or platform specific constraints on any of the
> technologies used.
Received on Wednesday, 1 October 2003 03:26:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:41:09 UTC