Ron Schmelzer wrote:
> A protocol influencing an architecture is a specific example of
> tight-coupling. That means that any change to protocol requires change
> to architecture. Hoo-boy, that's badness.
I have an embedded device that only does modbus. How do I make that device
talk
SOAP? I have a router that only talks ethernet and so does the switch that my
computer is connected to. How do I make it understand the semaphores I learned
in boy scouts so that I don't have to have an ethernet cable?
There are some choices that you have to make. Some of those affect
architecture. The non-commital architect is the one that creates that pile of
goo that noone can figure out and is never extensible because there's not a
standard anywhere to plug into.
Gregg Wonderly
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
