Web Services : SOAP, REST, XML, JSON
Get flash to fully experience Pearltrees
De plus en plus d’entreprises ont besoin de rendre leurs applications accessibles sur le web. Les motivations sont multiples : élargir l’audience des utilisateurs, vendre des services en ligne, faire communiquer des applications existantes ou supporter une interface de type AJAX. Dans ces conditions, quelle architecture choisir ou concevoir ? Quel format utiliser pour échanger des données sur le web ? Et devrait-on utiliser un protocole applicatif existant ou développer un protocole adapté à nos besoins ?
SOAP vs. REST : choisir la bonne architecture web services - Clever Link - Veille - Clever Age
SOAP end : The End Of The Road For Web Services - Simon Says...
Subscribe to this blog Computer industry veteran Simon Phipps is at large in the open source movement and sending dispatches with the latest news from the inside. A director at OSI, a C-level exec at open source identity startup ForgeRock and an activist in the software freedom movement, expect the unexpected, the fascinating and the infuriating.Google just announced that they are getting ready to kill their SOAP API . XML+SOAP was a good milestone in the history of integration but it is now time to look at the next milestone and that next milestone is JSON+REST. We briefly talked about that in abstract terms a couple of years ago but here are 3 simple reasons why: Browsers can consume large amount of JSON much more efficiently than they can consume large amount of XML and the gap is widening because the latest versions of the browsers are now providing native, safe support for encoding and decoding JSON.
JSON+REST vs. XML+SOAP | Building Feedly
Managing changes to APIs is hard. That is no surprise to anyone who has ever maintained an API of any sort. Web services, being a special case of API, are susceptible to many of the difficulties around versioning as other types of APIs. For HTTP based REST style web services the combination of resources and content negotiation can be used to mitigate most of the issues surrounding API versioning.
Peter Williams - Versioning REST Web Services
In my previous post on this subject I described an approach to versioning the API of a REST/HTTP web service. This approach has significant advantages over the approach that is currently most common (i.e. embedding a version token in the URL). However, it does have some downsides. This post is an attempt to outline those and to present some ways to mitigate the negative impacts. Using content negotiation to manage versions requires, by definition, the introduction of nonstandard media types.
Peter Williams - Versioning REST Web Services (Tricks and Tips)
Jean-Jacques Dubray takes issue with my approach of using content negotiation to manage service versioning in HTTP. I actually hesitate to respond to Mr. Dubray because the overall tone of his piece is rather off putting. On the other hand, he raises a couple of interesting questions which I have been really looking for and excuse to talk about.
Peter Williams - REST/HTTP Service Versioning (Response to Jean-Jacques Dubray)
One of the least well understood core tenets of the REST architectural style is that “hypermedia is the engine of application state”. Which basically means that responses from the server will be documents that include URIs to everything you can do next. For example, if GET a blog post the response document will have URIs embedded in it that allow you to create a comment, edit the post and any other action that you might want to do. Basically, this allows you to think of your application as a state machine with every page representing a state and links representing every possible transition from the current state . This approach means that to correctly be access your application the only things a client needs to know is a) a well know starting point URI and b) how to parse one of the document formats (representations) your application supports. For human facing web applications this approach is the one that is always used.
Peter Williams - Hypermedia as the Engine of Application State
In an exclusive nine-part dialogue with an imaginary eBay Architect , we present an accessible discussion of the REST vs. SOA issue. Although eBay have what they call a 'REST' interface, it is, in fact, a STREST interface, and only works for one of the many function calls that they make available via SOAP (GetSearchResults). Duncan Cragg: So - let's get straight to my argument: I claim that your SOAP APIs, as instances of the SOA style, won't scale or interoperate as well as they would if they were implemented in the REST style.
Getting Data | The REST Dialogues | What Not How | http://duncan-cragg.org/blog/
The vast majority of supposedly 'REST' Web APIs are simply abusing HTTP to carry function calls. I call these APIs 'Service-Trampled REST', or STREST. STREST APIs come with specific costs which could stifle the two-way data Web (Web2.0) if allowed to propagate unchecked.
STREST (Service-Trampled REST) Will Break Web 2.0 | What Not How | http://duncan-cragg.org/blog/
The following post was written by Manu Sporny, Digital Bazaar’s Founder and CEO. Recently a few XML experts have been claiming that the decision made by large Web Service providers, like Twitter and Foursquare, to drop XML from their Web Services infrastructure is not very interesting news. They also assert that the claims that JSON is more useful than XML for the majority of Web Services is wishful thinking by a “cadre of Web API designers” that have yet to provide “richer APIs”.
Web Services: JSON vs. XML ? Digital Bazaar
Linked Data for JSON « Digital Bazaar
So, the way that we write these applications are distributed now, we use distributed protocols to get data, but the data that we retrieve remains locked in the old way of thinking about application data. That is – we tend to think of data as local to our computers, not global to the world. There is no widely-used global naming scheme for the data that we retrieve from websites. One could argue that we have XML , but that doesn’t identify data in a global way unless the developer builds that information into the data model. Modifying the data model of XML is difficult because it requires you to modify document schema, which is a very time consuming process – and in some cases, impossible if you do not own the document schema. We do have RDF , but most web developers don’t know what it is.Activity Streams Working Group: JSON Activity Streams 1.0
Abstract This specification details the serialization of a stream of social activities using the JSON format. Activities are important in that they allow individuals to process the latest news of people and things they care about. In its simplest form, an activity consists of an actor , a verb , an an object , and a target . It tells the story of a person performing an action on or with an object -- "Geraldine posted a photo to her album" or "John shared a video".Essentially, I'm just riding on JSLint's coattails. The name 'lint' was originally used to find problems in C source files. It's not really valid here because JSON is just a protocol. Shameless? You bet!