background preloader

Web Services : SOAP, REST, XML, JSON

Facebook Twitter

Open APIs: State of the Market, May 2010. SOAP vs. REST : choisir la bonne architecture web services - Clever Link - Veille - Clever Age. De plus en plus d’entreprises ont besoin de rendre leurs applications accessibles sur le web.

SOAP vs. REST : choisir la bonne architecture web services - Clever Link - Veille - Clever Age

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 ?

Table des matières Introduction Nous parlons ici de mettre en place un protocole applicatif sur le web pour échanger de l’information avec un grand nombre de clients. Le développement de protocoles applicatifs Rendre ses applications accessibles sur le web consiste à définir un protocole applicatif et un format de données. Nous avons vu que les motivations des entreprises pour déployer des web services aujourd’hui étaient nombreuses. SOAP end : The End Of The Road For Web Services. Subscribe to this blog About Author With a focus on open source and digital rights, Simon is a director of the UK's Open Rights Group and president of the Open Source Initiative.

SOAP end : The End Of The Road For Web Services

He is also managing director of UK consulting firm Meshed Insights Ltd. Contact Author. JSON+REST vs. XML+SOAP. Architectural Styles and the Design of Network-based Software Architectures. Peter Williams - Versioning REST Web Services. Peter Williams - Versioning REST Web Services (Tricks and Tips) In my previous post on this subject I described an approach to versioning the API of a REST/HTTP web service.

Peter Williams - Versioning REST Web Services (Tricks and Tips)

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. There is really no way around this. The browser not working is a pretty big issue. Unfortunately, I don’t really have a great general solution for browsers. Curl One advantage of having the version token directly in the URL is that it makes it really easy to use curl against the service. Peter Williams - REST/HTTP Service Versioning (Response to Jean-Jacques Dubray) Jean-Jacques Dubray takes issue with my approach of using content negotiation to manage service versioning in HTTP.

Peter Williams - REST/HTTP Service Versioning (Response to Jean-Jacques Dubray)

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 - Hypermedia as the Engine of Application State. One of the least well understood core tenets of the REST architectural style is that “hypermedia is the engine of application state”.

Peter Williams - Hypermedia as 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.

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). In this dialogue series, I argue the case for eBay to adopt a truly REST approach to their integration API. Part 1: Getting Data 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.

eBay Architect: SOA won't scale or interoperate and REST will? eA: And even if it is true, we don't care about scalability and interoperability: we have quite low traffic on our APIs - certainly compared to port 80; plus we're eBay so we don't need to interoperate with anyone. STREST (Service-Trampled REST) Will Break Web 2.0. The vast majority of supposedly 'REST' Web APIs are simply abusing HTTP to carry function calls.

STREST (Service-Trampled REST) Will Break Web 2.0

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. Although 'mashability' is a supposed benefit of the current proliferation of APIs, true interoperability and scalability can only be guaranteed by true REST interaction. This is not an academic, purist or aesthetic stance, but one based on practical consequences, as I will explain. Designing HTTP Interfaces and RESTful Web Services (Confoo11 2011-0... Web Services: JSON vs. XML ? Digital Bazaar. The following post was written by Manu Sporny, Digital Bazaar’s Founder and CEO.

Web Services: JSON vs. XML ? Digital Bazaar

This page is also available in Spanish. Thanks to Maria Ramos from Web Hosting Hub for doing the translation. 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. Linked Data for JSON « Digital Bazaar. A global model for sharing information, once a dream, and then a reality with the Internet and the Web, is now becoming a fundamental part of the systems that we build.

Linked Data for JSON « Digital Bazaar

As we automate much of the sharing of information, we need to be able to express this shared data to computers in a way that is both easy for them to process and also easy for web developers to understand. The foundational standards of the web, specifically global naming conventions (IRIs), distributed computing (web servers and clients) and remote data access (TCP/IP and HTTP) are positively impacting the way we build software.

One of the areas that this standardization is lacking is with the way that we build data services for the Web using JSON. This article discusses some new work that attempts to merge the power of Linked Data with the simplicity of JSON. The world is slowly starting to depend on Web browsers to provide functionality that our desktop applications have historically provided. Zero Edits Compatibility. Orderly JSON. 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.

Activity Streams Working Group: JSON Activity Streams 1.0

Activities are important in that they allow individuals to process the latest news of people and things they care about. Table of Contents 1. Introduction2. 1. In its simplest form, an activity consists of an actor, a verb, an an object, and a target. JSONLint - The JSON Validator.