> Every article has a different definition. Every 'consultant/analyst' > report/<insert your favorite color here> -paper says everyone should be > doing 'it', and if you're not, you're not 'agile', or competitive, or ... > Major FUD factor here.
Is it just me, or does no one in the computer science field get taught how to do basic literature searches for past inventions? *Major* ancient history. All SOA is is a way to wrap existing apps in a framework, find the apps in a directory, and communicate input and results in a standardized way. Doesn't solve the problem of who can use the app, how it should be used, or whether the app is even useful in that form. It's just a rehash of object wrapper/broker capability published in the XNS Reference Architecture circa 1972 or so. Or NCS. Or Corba. Or DOM. Or any of dozens of other distributed object reference technologies over the past 3-4 decades. I annoy numerous people every time I point out that there is absolutely nothing new about this concept, and have them actually do the homework on how their SOA commentary or strategy is different that the dozen or so times this has been tried before. I ask them to focus on why the previous efforts failed, both technically and organizationally. Usually, they don't come back. -- db ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
