How can something called SOAP be such filthy shit. No wonder people wanted to build local-only software back then.

fucking hell I never looked at it that way 🤣🤣

wtf is soap?

Don't get it either, xmlrpc all the way. But anyway, .NET had native integration with soap. You could access functions like they were local, there was no difference. The tooling made SOAP cool. But if you do it with a bad soap client, it sucks.

Whats wrong with soap? It's a bit dated and verbose but it works fine. I mean all of xml is pretty verbose anyway

@antigermgerm it's stuff you use to clean yourself, and make yourself less smelly. no wonder you never heard of it.

@antigermgerm the predecessor of REST

@retoor yeah, I need to migrate a .NET codebase making API calls via SOAP. Tons of templates, weird signing with antiquated certificates, etc.. End of the story: What takes me 30 seconds and 10 lines with a rest API, it took me 2 weeks and tons of AI to analyse how to make one request.

@n1cK1337 should've used a. Net client :p

It's a protocol where the S stands for Simple. Those are always a horror show. They have the need to market as simple as either they are simply not or it's too simple shifting way too much complexity and little standardisation to the implementation.
Examples:
SNMP, SMTP, SNTP, SSDP etc.