3 ms·
Also, SOAP libraries (e.g. Soap4r) are problematic (doesn't talk to Micro$soft's version of SOAP properly). I feel this point never quite lands home with peopl
by andrewf 16y ago
Also, SOAP libraries (e.g. Soap4r) are problematic (doesn't talk to Micro$soft's version of SOAP properly).
I feel this point never quite lands home with people who've never tried to use SOAP across ecosystems (ie not .NET-.NET, Glassfish-Glassfish, etc).
Put in plain terms: It just doesn't fucking work.
- reinhardt 16y agoI've never had to use SOAP so I may be off here but isn't the above "just" a matter of bad implementations and not necessarily SOAP itself ? It sounds like blaming HTML/CSS/Javascript because there are crappy browsers that don't follow the standards.
- andrewf 16y agoI think a lot of it comes down to SOAP, and related standards, being ambiguous and changing enough over time that even if you follow the standards, it isn't necessarily clear what you can and should do. Take a look at WS-I, the standard which tells you just how you should implement all of the standards that came before it, if you actually want to talk to other implementations: http://ws-i.org/profiles/BasicProfile-1.2-WGD.html http://ws-i.org/profiles/BasicProfile-1.2-WGD.html I first looked at SOAP in 2007. It made more sense to me after I read this: http://wanderingbarque.com/nonintersecting/2006/11/15/the-s-stands-for-simple/ http://wanderingbarque.com/nonintersecting/2006/11/15/the-s-...
- deleted 16y ago[deleted]