Luckily my exposure seems to be restricted to legacy and enterprisey stuff nowadays.
There is no political intent behind this site. It is meant to be a joke. A joke with a grain of truth.
Backstory: I was waiting for a conference call, saw that stopsoap wasn't registered and put this together in 15min.
Deeper backstory: I'm the co-founder & CEO of Simple.com. We deal with many SOAP APIs. The upside is that SOAP provides very clear specifications as to how the API is supposed to work. The downside, is that things rarely work as expected. It is frustrating, but such is life in banking.
On a more serious note, We're Hiring. If you'd like to work at Simple, where we replace you bank & give you clean REST APIs to your finances, check us out: http://simple.com
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.
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.
I think it's terribly important that it be possible for the community to reflect, critically: SOPA is a serious issue, one we should all be concerned about, and more importantly taking action against. However, there is a point where it becomes an echo chamber, where we are preaching to the choir. Having nearly every submission be yet another "X is blacked out" does not necessarily correlate to communicating to our lawmakers that we do not want this legislation to pass.
Clearly this subtle, yet provocative submission's intent to communicate such a critique was understood by a number of people. I'm still unsure how it ended up bumped so quickly, but whatever the case, I hope the point wasn't entirely lost on those of you who didn't appreciate it.
SOAP services also usually include a WSDL, which is alternately said to stand for Web Service Definition List, Web Service Definition Language, or Web Service Description Language and is meant to define the methods and parameters available to the client.
Because the whole system is so complicated, cumbersome and over-engineered, the normal way to create a WSDL is to do it automatically using tooling. Unfortunately, different frameworks generate different and often mutually incompatible and non-interoperable WSDLs. So, for example, a .NET SOAP client might not be able to consume a WSDL generated by a Java framework.
The S in SOAP originally stood for "Simple", but the protocol is anything but.
SOAP is a protocol specification for executing remote procedure calls over a network. SOAP uses XML for its message formatting and data serialization, and (usually) HTTP for its network protocol.
JSON, on the other hand, is a data serialization format rather than a remote procedure call format. It is sometimes used in web services - especially services based on Representational state transfer (REST) - to pass structured data between the client and server, but it is not a remote procedure call protocol in itself.
REST, in turn, is a method for designing a web service so that its functionality is accessed the same way that HTTP works. In REST, the service is organized into resources and methods, with resources corresponding to URLs and methods corresponding to the HTTP request methods: chiefly GET, POST, PUT and DELETE.
If you want to access a resource, you issue an HTTP GET request on the URL corresponding to that resource. If you want to create a resource, you issue an HTTP POST request on the URL corresponding to that resource with the data you want to post in the request body. If you want to update an existing resource, you issue an HTTP PUT request on the corresponding URL with the updated data. If you want to delete a resource, you issue an HTTP DELETE request on the corresponding URL.
Recently, many REST web services are designed to accept request data in JSON format and to send responses in JSON as well. Since web services are mainly consumed by client programs (rather than by humans browsing), JSON allows for a generic data structure that the client can consume and parse more easily than HTML, which is designed more specifically to structure documents.
*sorry, reddit is down
Actually, swell guy. I'm still wondering how he created such a mess.
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.