Well in contrary to the SOPA people, the SOAP people aren't trying to forcibly push SOAP on all of us with laws and treaties. There's enough alternatives. Let them use SOAP :p
Agreed, When i started SOAP around 2000, it was very simple. After that we for more into the awful WSDL 1 (WSDL 2 is better). But the number of WS-* and the different implementations that are all incompatible is just a nightmare.
In 2001 I gave a talk (I believe at OSCon, to a packed audience) titled "Why SOAP Sucks". I started with a print-out of all the specs required to implement SOAP fully (there were lots of incomplete implementations around at the time, but barely any complete ones). It was more than two reams of paper (around 1100 pages of spec, if I recall). It had quite an "impact".
IIRC, the Table of Contents for the SOAP spec is bigger than the entire XML-RPC spec, yet SOAP offers little practical advantage. Luckily many new RPC implementations bypass both SOAP and XML-RPC and are looking to REST. $deity help all of us who need to work with legacy SOAP, however...
I can totally relate to these two articles, having recently attempted to write a .NET SOAP client for a web service that uses the (non-standard) SOAP with Attachments method for sending binary data. For something that was created to provide simple interoperability, SOAP is rife with a ridiculous number of inconsistencies and competing mini-(non)standards.
Not a coincidence. Simple to implement != simple to explain to your boss (`it's standard industry practice'). The name is meant to sell the standard to non-techies.
I'll admit to being completely ignorant about the benefits of using SOAP to communicate between servers. However I can say that for server->client communication it is the worse data representation I've ever had to work with and I genuinely hope we see the end of it. JSON maybe not be perfect, but it's so much better at delivering a structured data model then xml is.
I think I'd like JSON as a data representation a lot more if schemas for it were more prevalent. I've noticed it's a lot harder to generate valid JSON -- or rather a lot harder to escape data. With XML, this is fairly trivial. Granted, my use case is considerably different from most.
The other idea from SOAP I'd love to see applied to ReST is a descriptor document for the API. Given how poorly many ReST APIs are documented, I do miss the good 'ol WSDL. Plus, it gave me some measure of security that the API didn't change.
The strictness in generating valid json is exactly why i like it so much. I've worked with too many SOAP services with nodes and attributes thrown lazily around the document simply because xml is so unstructured. I do agree however that json could use a few more built-in data types to handle more complex use cases.
Unfortunately I spent a couple years building web services tools in 2002,3. I have long since repented. Love the "S stands for Simple" link... fantastic dialog!
So much efforts to stop law proposal X.
Which is great.
What about the idea of a Open-USA or other Open-Iran where a true Meta-Democracy or whatever open society model is implemented where all efforts would be PRO something instead of hateful stuff like protesting.
This laws are proposed by lobbies that go against the interest of 99% of the persons. How is that even conceivable ?
All this big companies opposing could create a github project for open government and then elect a person that implements that.
I agree. Sure discussions about SOPA have their place here, but lately it just felt like a bit echo chamber where you have the same people preaching to the choir using the same arguments over and over again.
If I look at the homepage right now it seems half the posts are "site XXX blacked out to protest SOPA". Do all those need a separate story? The redditization of HN is running wild.
Indeed. Another irony, the Cheezburger Network sites are using a pop-up complaining about SOPA, when arguably they are just the sort of site there is a legitimate complaint about, as they routinely rip off other people's comments, and bask in the ad revenue.
I think what the OP meant is that this story is meant as a parody of the avalanche of "sopa is evil" posts lately. Whether you know what SOAP is or not is beyond the point.
The population of HN isn't just anti-SOPA because it's fashionable. SOPA would directly affect small internet businesses by putting the onus of copyright policing on site owners. Considering how many of the HN startups have any user generated content at all, it's a real concern for the vast majority of them. To not advocate against SOPA would be foolish.
75 comments
[ 3.0 ms ] story [ 159 ms ] threadhttp://www.en2palabras.com/f10/mafalda-nos-explica-que-es-la...
Mirror:
http://www.taringa.net/posts/info/13583646/Mafalda-nos-expli...
Luckily my exposure seems to be restricted to legacy and enterprisey stuff nowadays.
The other idea from SOAP I'd love to see applied to ReST is a descriptor document for the API. Given how poorly many ReST APIs are documented, I do miss the good 'ol WSDL. Plus, it gave me some measure of security that the API didn't change.
http://www.w3.org/Submission/wadl/
What about the idea of a Open-USA or other Open-Iran where a true Meta-Democracy or whatever open society model is implemented where all efforts would be PRO something instead of hateful stuff like protesting.
This laws are proposed by lobbies that go against the interest of 99% of the persons. How is that even conceivable ?
All this big companies opposing could create a github project for open government and then elect a person that implements that.
*sorry, reddit is down
http://www.microsoft.com/presspass/exec/de/Box/default.mspx
Actually, swell guy. I'm still wondering how he created such a mess.
If I look at the homepage right now it seems half the posts are "site XXX blacked out to protest SOPA". Do all those need a separate story? The redditization of HN is running wild.
Will september ever end?
In the current economy, consultants specialized in fixing convoluted web applications need us more than ever.