[prev] [thread] [next] [lurker] [Date index for 2004/04/01]
Today I heard a story about a load-balancer. That load-balancer had a SOAP interface for managing it.. What's that crap? What about SNMP??? SNMP is way older than SOAP and supported by way more management softwares than some proprietary SOAP implementation. You see, I don't have a problem with the idea of SOAP, I have huge problems with the specification and implementations of it. SOAP is supposed to be cross-platform and work with "any" language. But seriously, how many SOAP libraries are known to work well with each other (note the "well"). SOAP is probablly as bloated as CORBA these days except it's a lot easier to read what's transmitted by human. The big problem I see with SOAP is that the specification is too loose, you can do the same thing in many different ways and all implementations (ofcourse) do it differently. Why did they invent SOAP in the first place? - Is it because w3c or whoever didn't like CORBA? - Is it because the crack-monkeys have been set loose in the XML-era? - Is it because there-is-so-much-bandwidth-so-I-don't-care-if-a-message-is-huge? Instead of trying to solve the problem by inventing a whole new protocol - why not sit down, identify the problems, write a tight specification and invent some "100% SOAP compliant" quality certification??? Problem is we're still only human and it's in our nature to disagree. /Claes
Generated at 14:02 on 01 Jul 2004 by mariachi 0.52