3 ms·

Obligatory link to "The S stands for simple", a SOAP-bashing classic: http://harmful.cat-v.org/software/xml/soap/simple http://harmful.cat-v.org/software/xml/so

by nathell 10y ago

Obligatory link to "The S stands for simple", a SOAP-bashing classic: http://harmful.cat-v.org/software/xml/soap/simple http://harmful.cat-v.org/software/xml/soap/simple

codeulike 10y ago
Everything must be in XML. Except the SoapAction header. Which has no defined standard. Yeah I remember all that madness.
- jgalt212 10y ago
  remember? Thomson Reuters on demand APIs are still largely SOAP based.
  - fs111 10y ago
    never touch a running system...
    - jgalt212 10y ago
      fair enough, but I posit X users started consuming this API when SOAP was prevalent and Y users started when ReST was prevalent and Y >> X. Furthermore, SOAP is hard to maintain these days because it's so ancient. i.e. the libraries are not new and/or actively maintained. As such, I maintain SOAP should be gone for the good of the running system.
      - creshal 10y ago
        In Python you simply don't have good SOAP libraries. They were all started at the tail end of its popularity and then all died quiet deaths when attention shifted to ReST before they were actually production ready, and if you now want to talk to a SOAP service… well, better don't do it in Python. 2, that is. Forget about 3.
        corford 10y ago
        Have you seen Zeep? It's literally billed as "A fast and modern Python SOAP client". Python 2 and 3 compatible. Last commit was two weeks ago. http://docs.python-zeep.org/en/master/ http://docs.python-zeep.org/en/master/
        creshal 10y ago
        Nope. We needed one last September, zeep didn't yet exist back then. And going by the bugtracker, it's running into quite a few problems with almost-but-not-quite compliant servers/WSDL files, which is a real issue when you're trying to interface ass-old legacy APIs (we're talking "not upgraded since 2006"-old) made by $BigEnterprise. Maybe this time the project won't die before they work out all the little kinks.
  - fluxquanta 10y ago
    I'm working with a very well-known American company with over $4b annual revenue that shall remain nameless and is currently developing a new SOAP API to replace the existing "dump a CSV on an FTP server" integration.
sytringy05 10y ago
"Let me tell you about UDDI" Nooooooooooooooooo. Everytime someone says "service discovery" a kitten dies (Except for consul, that's the biz).
lmm 10y ago
If that was ever true it certainly doesn't seem to be true now. All the tools support WSDL-first. All the tools are compatible with each other. Fill in the URL, let it autogenerate the interface, write your code and it all just works.
- SolarNet 10y ago
  Because it was the latest trend 10+ years ago, and now people have made it just work because their applications are all built on it and people need actually good tools to use these architectures. It's always about tools, it's not like TCP is the best protocol or anything, it just has the best tooling, ditto for C, POSIX, etc. anything can be a good standard after 15+ years of work on it. Containers will be like that in a couple of years. It's all just cycles man.

by nathell 10y ago

Obligatory link to "The S stands for simple", a SOAP-bashing classic: http://harmful.cat-v.org/software/xml/soap/simple http://harmful.cat-v.org/software/xml/soap/simple

codeulike 10y ago

Everything must be in XML. Except the SoapAction header. Which has no defined standard. Yeah I remember all that madness.

jgalt212 10y ago
remember? Thomson Reuters on demand APIs are still largely SOAP based.
- fs111 10y ago
  never touch a running system...
  - jgalt212 10y ago
    fair enough, but I posit X users started consuming this API when SOAP was prevalent and Y users started when ReST was prevalent and Y >> X. Furthermore, SOAP is hard to maintain these days because it's so ancient. i.e. the libraries are not new and/or actively maintained. As such, I maintain SOAP should be gone for the good of the running system.
    - creshal 10y ago
      In Python you simply don't have good SOAP libraries. They were all started at the tail end of its popularity and then all died quiet deaths when attention shifted to ReST before they were actually production ready, and if you now want to talk to a SOAP service… well, better don't do it in Python. 2, that is. Forget about 3.
      - corford 10y ago
        Have you seen Zeep? It's literally billed as "A fast and modern Python SOAP client". Python 2 and 3 compatible. Last commit was two weeks ago. http://docs.python-zeep.org/en/master/ http://docs.python-zeep.org/en/master/
        creshal 10y ago
        Nope. We needed one last September, zeep didn't yet exist back then. And going by the bugtracker, it's running into quite a few problems with almost-but-not-quite compliant servers/WSDL files, which is a real issue when you're trying to interface ass-old legacy APIs (we're talking "not upgraded since 2006"-old) made by $BigEnterprise. Maybe this time the project won't die before they work out all the little kinks.
- fluxquanta 10y ago
  I'm working with a very well-known American company with over $4b annual revenue that shall remain nameless and is currently developing a new SOAP API to replace the existing "dump a CSV on an FTP server" integration.

sytringy05 10y ago

"Let me tell you about UDDI" Nooooooooooooooooo. Everytime someone says "service discovery" a kitten dies (Except for consul, that's the biz).

lmm 10y ago

If that was ever true it certainly doesn't seem to be true now. All the tools support WSDL-first. All the tools are compatible with each other. Fill in the URL, let it autogenerate the interface, write your code and it all just works.

SolarNet 10y ago
Because it was the latest trend 10+ years ago, and now people have made it just work because their applications are all built on it and people need actually good tools to use these architectures. It's always about tools, it's not like TCP is the best protocol or anything, it just has the best tooling, ditto for C, POSIX, etc. anything can be a good standard after 15+ years of work on it. Containers will be like that in a couple of years. It's all just cycles man.