Todd Biske wrote:
> There are still too many people out there in the
> industry who think that interfaces should be set once and never touched.
Sometimes, changing an interface is not a "choice". Some technologies don't
afford that flexibility. You need to chose a platform and exploit the related
technologies to create the flexibility you need. Understanding how to apply
the
technologies of your platform and understanding the choices that other
platforms
provide is key.
I am an amatuer radio licensee in the U.S. I have a mobile station that is
subjected to the radiated noise from spark plugs and fuel injectors. I can't
change the operations of the system, end to end, but I can change out the
transport layer of the spark to use shielded wiring, and I can attach some RF
chokes in various places where I can't replace wires. But, in the end, the
interface is designed exactly the way it is, and I can't change that. I have
to
understand the technology (RF emission and noise) to address the issues at hand.
In the software world, spark plugs might be like SMB traffic on the network.
It's constantly there, you can't change the interface to that service, it's
controlled by someone else. But, there are completely different technologies
which provide similar features, but without the same level of integration with
the native platform. So, what do you do for file sharing and printing in the
windows world if you don't want SMB traffic buzzing across your network
constantly?
There are choices to be made. Understanding all the possibilities is
difficult.
Standards help, but look at SMB, SMTP, HTML and the handful of other
technologies which all provide ways for viruses to be transported to our
computers. A standard doesn't always provide the most bang for the buck.
You need to be prepared to absorb, comprehend, and apply the information
related
to the technologies that you work with. It's a cold cruel world :-)
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/
