3 ms·
My worst memory of SOAP was dealing with an attachments API that required each byte in a byte array to be wrapped in an XML element. You ended up transferring
by chrisbroadfoot 16y ago
My worst memory of SOAP was dealing with an attachments API that required each byte in a byte array to be wrapped in an XML element.
You ended up transferring ~10x the size of the file. I suppose gzip would have helped somewhat.
- ZoFreX 16y agoMy worst memory of SOAP is using it. Experienced it for the first time ever a couple of weeks ago (all I've used before now is ad-hoc JSON or XML apis, mostly JSON) and (knocks on wood) never, ever again. The article touches on a few of the things I really didn't like about it, the main one being the expectation that you will use tooling to generate code rather than the contract first, and that every time I hit a hurdle and switched to a different library, I had to start over.
- deleted 16y ago[deleted]
- GFischer 16y agoThat is awful, and I'd never defend that implementation, but you can compress http (sorry if by "gzip would have helped" you meant that) http://en.wikipedia.org/wiki/HTTP_compression http://en.wikipedia.org/wiki/HTTP_compression