W3C home > Mailing lists > Public > www-ws-arch@w3.org > July 2002

Generic/specific connectors

From: Mark Baker <distobj@acm.org>
Date: Mon, 22 Jul 2002 17:41:01 -0400
To: "Newcomer, Eric" <Eric.Newcomer@iona.com>
Cc: www-ws-arch@w3.org
Message-ID: <20020722174101.V1586@www.markbaker.ca>

(woohoo, got email)

Hi Eric,

> Anyway, let me try to summarize my views for a new thread and let's see if we can move toward convergence.

Rather than respond to that point in the new thread, I'll just respond
here.  You suggest that the architecture should permit both generic and
specific interfaces.

I suggest that this is either impossible, or that you are in effect
designing two systems, depending upon whether you think that's a valid
thing to do or not - I don't think it is.  As you define the rest of
the architecture, you won't be able to assume anything about connector
semantics, which will impact the overall architecture substantially.

Architectural constraints are a *good* thing, not a bad thing.  They
don't necessarily (like generic interfaces) restrict *what* can be
done, only *how* they're done.  You can have too many, as Gopher
demonstrated, but you can also have too few.  Web services provide too
few constraints because they're missing the architectural constraint
that *EVERY* single successful system on the Internet has; generic
connector semantics.

Mark Baker, CTO, Idokorro Mobile (formerly Planetfred)
Ottawa, Ontario, CANADA.               distobj@acm.org
http://www.markbaker.ca        http://www.idokorro.com
Received on Monday, 22 July 2002 17:28:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:40:57 UTC