The S stands for Simple (2006)

Re:The S stands for Simple (2006) by ksherlock on Wednesday May 20, 2015 @01:01PM (#9577627)

Just wait... I predict a Show HN: SOAP over (nntp/finger/bitcoin block) written in (go/rust/coffeescript/haskell) within 24 hours.

[ Parent | on HN ]

Re:The S stands for Simple (2006) by hackcasual on Wednesday May 20, 2015 @01:26PM (#9577795)

I 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.

[ Parent | on HN ]

Re:The S stands for Simple (2006) by 0xdeadbeefbabe on Wednesday May 20, 2015 @02:29PM (#9578193)

Go isn't cool I hope, but clojure is definitely cool. I know because they have long, sometimes blue, hair.

[ Parent | on HN ]

Re:The S stands for Simple (2006) by rwmj on Wednesday May 20, 2015 @05:44PM (#9579530)

How about SOAP written using OCaml with macros?

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).

[ Parent | on HN ]

Re:The S stands for Simple (2006) by hackcasual on Wednesday May 20, 2015 @06:00PM (#9579618)

Oof. 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.

[ Parent | on HN ]