3 ms·
SOAP in a nutshell: > SG: Well, officially none. But you can potentially support any of ‘em. And there’s lots of platforms that support JMS, and FTP, and SMTP.
by hackcasual 11y ago
SOAP in a nutshell:
> SG: Well, officially none. But you can potentially support any of ‘em. And there’s lots of platforms that support JMS, and FTP, and SMTP.
> Dev: Does anyone actually use these other transports?
- ksherlock 11y agoJust wait... I predict a Show HN: SOAP over (nntp/finger/bitcoin block) written in (go/rust/coffeescript/haskell) within 24 hours.
- hackcasual 11y agoI doubt SOAP is cool enough to attract the go/rust/etc... crowd. So back in SOAP's infancy, company firewalls were a fucking mess, so being able to use something that was likely to just work across myriad internal networks was a boon. I'm a suspicious man, and am willing to bet the whole "we're transportation agnostic" was more a smoke screen for "we need to drill holes in your firewall" than a particular architectural love for passing SOAP messages over SMTP.
- 0xdeadbeefbabe 11y agoGo isn't cool I hope, but clojure is definitely cool. I know because they have long, sometimes blue, hair.
- rwmj 11y agoHow about SOAP written using OCaml with macros? http://git.ocamlcore.org/cgi-bin/gitweb.cgi?p=ocsoap/ocsoap.git;a=tree;f=src;h=3c2c51074973b2d0c1d07fb9443622f2cda8a189;hb=HEAD http://git.ocamlcore.org/cgi-bin/gitweb.cgi?p=ocsoap/ocsoap.... Back when I wrote that I was trying to call the Google AdWords API -- it was entirely SOAP based, and awful (still could be for all I know).
- hackcasual 11y agoOof. I guess I shouldn't hate too much as there are still some API's out there that use it. Exchange I'm looking at you.