PUBLIC MARKS with tags web & rest

The Django REST interface is a Summer of Code project that implements a general method offering a public and private API for existing Django models. New generic views will simplify data retrieval and modification via different web services in a resource-centric REST architecture, providing model data in formats such as XML, JSON and YAML with very little custom code. The REST interface consists of two major parts: 1. Easily configured Create/Read/Update/Delete (CRUD) method access patterns for models. 2. Resources that don't correspond 1:1 to models. More information: * Initial proposal * First mail to django-developers

an outline for what a restful semantic web services would look like.

J'espère que ce billet vous aura permis de comprendre un peu mieux les règles qui régissent une architecture REST et par extension une architecture orientée ressource. Il ne s'agit pas de la nouvelle architecture 2.0 hype du moment mais bien du Web passé, actuel et futur donc en le comprenant vous pourrez construire des sites et des applications web mieux pensées et cohérentes.

As an educational tool, this article will describe how to re-engineer a familiar application, email, as a Web Service using HTTP and the principles of Web Architecture and REpresentational State Transfer.

« Si vous essayez de comprendre REST, cette série est faite pour vous. »

Un grand classique de l'explication de REST enfin traduit, merci Karl !

Appelez les pipes, teqlos, dapps, modules, mashups ou n’importe quoi d’autre, le fait est que nous avons récemment vu un bon nombre de nouveaux services permettant aux développeurs et aux utilisateurs de construire de petites applications et des mashups pour transformer et ré-utiliser des données. Nous vous présentons dans ce qui suit 5 applications qui permettent de mélanger, déformer et réorganiser vos données, en examinant les données entrantes, sortantes, le support du REST, des suggestions d’utilisation et le niveau de compétence requis

"A complex system that works is invariably found to have evolved from a simple system that worked." --John Gall, Systemantics To design a website you need to know about HTTP, XHTML, and URIs. To design a web application you need to know about HTTP, XHTML, and URIs. To design a web service you need to know about XML, SOAP, WSDL, UDDI, WS-Policy, WS-Security, WS-Eventing, WS-Reliability, WS-Coordination, WS-Transaction, WS-Notification, WS-BaseNotification, WS-Topics, WS-Transfer... What happened there? The web is the most successful distributed platform in the world, and it's simple enough for average humans to understand. How come adapting it for use by computer programs requires that smart people spend billions of dollars and devote years of their lives to coming up with all these new standards? And what happened to HTTP and URIs? The answer is that "Web Services" aren't the web. They're a heavyweight architecture for distributed object access, like COM and CORBA. This architecture is associated with the web, because HTTP is a trendy protocol, and flexible enough that you can implement almost anything on top of it. But it's not really of the web. The architecture of Big Web Services reinvents or ignores every feature that makes the web successful. This is the book that puts the "web" back into "web services". You can design a web service that uses HTTP, XHTML, and URIs. You just need to understand REST, the architectural principles that drive the web. RESTful Web Services gives you the tools you need to argue for sensible web services, and the strategies and code you need to create them. The book is manuscript complete at around 440 pages, and it'll be published by O'Reilly in May 2007. We think this can be the definitive work on the real-world use of REST.