public marks

PUBLIC MARKS from pvergain with tag rest

July 2007

django-rest-interface - Google Code

by 1 other (via)
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

May 2007

MicroApps -

by 2 others
MicroApps are small REST applications that are designed from the ground up to be integrated with other applications. Usually, they are not directly useful on their own, but must be integrated into other applications (this is what differentiates a MicroApp from a regular REST application).

March 2007

RESTful Web Services

"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.

February 2007

Ajax and REST, Part 1

The more that server-side Web applications become immersive by following rich-application models and delivering personalized content, the more their architectures violate Representational State Transfer (REST), the Web's architectural style. These violations can decrease application scalability and increase system complexity. By achieving harmony with REST, Ajax architecture lets immersive Web applications eliminate these negative effects and enjoy REST's desirable properties. In just 15 years, the World Wide Web has grown from a researcher's experiment to one of the technological pillars of the modern world. Originally invented to let people easily publish and link to information, the Web has also grown into a viable platform for software applications. But as applications have become more immersive by using rich application models and generating personalized content, their architectures have increasingly violated Representational State Transfer (REST), the Web's architectural style. These violations tend to decrease application scalability and increase system complexity. The emerging Ajax Web client architectural style lets immersive Web applications achieve harmony with the REST architectural style. They can enjoy REST's desirable properties while eliminating the undesirable properties experienced when an application violates REST's principles. This article explains how and why Ajax and REST succeed together for immersive Web applications.

pvergain's TAGS related to tag rest

ajax +   architecture logicielle +   django +   google +   javascript +   python +   ruby +   web +   web development +   web2.0 +