3 ms·
Personally, I think SOAP tooling can be a very leaky abstraction - things are great (e.g. adding a reference to a web service in Visual Studio is trivial) but t
by arethuza 9y ago
Personally, I think SOAP tooling can be a very leaky abstraction - things are great (e.g. adding a reference to a web service in Visual Studio is trivial) but then when something doesn't work quite as expected (particularly when calling between different tech platforms) debugging could be a nightmare.
My experiences with SOAP were that 99% of the time it was fine - but those other 1% seems to take the other 99% of my time... ;-)
- fuhrysteve 9y agoYes, my experience with SOAP is that even well written and maintained clients only work out-of-the-box with like half of the vendor-supplied services you come across. In many cases, I'll simply formulate xml requests myself and use a generic http request client because the implementation ended up being simpler & easier to maintain than all the confusing hacks I had to do to make zeep or suds (the most popular SOAP clients implemented in python) function properly.