The S stands for Simple
72.249.21.88
The S stands for Simple
1–10 of 54 posts
Re: The S stands for Simple
#2The server seems to be back online, but in case it goes down again (or changes IP or whatever), I have mirrored it here:
Re: The S stands for Simple
#3Did anybody else hear the SOAP Guy's lines in a voice that sounds like a cross between a used car salesman and Foghorn Leghorn?
Also, I like Google's protocol buffers library. It's straightforward, fast, has really nice bindings for C++, Java, and Python, and we know it's stable because it's what Google uses for most of its internal RPC stuff.
Re: The S stands for Simple
#4Interoperability is a vitally important but hard problem. CORBA and then SOAP have been thoroughly adopted, then widely condemned.
What's next?
Re: The S stands for Simple
#5I'm working on some SOAP stuff at work. I think it was a ploy to make me want to quit.
Re: The S stands for Simple
#6Interoperability is a vitally important but hard problem. CORBA and then SOAP have been thoroughly adopted, then widely condemned. What's next?
REST, Thrift, AMQP + protobuffs.
Re: The S stands for Simple
#7Interoperability is a vitally important but hard problem. CORBA and then SOAP have been thoroughly adopted, then widely condemned. What's next?
bert-rpc.org
Re: The S stands for Simple
#8I have to say that SOAP didn't even seem like a good idea at the time.
Re: The S stands for Simple
#9Its been my experience that anything with Simple or Lightweight as one of the letters in the acronym is usually anything but.
Re: The S stands for Simple
#10Its been my experience that anything with Simple or Lightweight as one of the letters in the acronym is usually anything but.
SNMP, for instance.
"The Stupid, it burnnnsss!"