django_restful

TwitterFacebook
Get flash to fully experience Pearltrees
This time around, I will try to take the logical next step with my exploration of REST and Django, and begin creating a Django contribution to implement the ideas I have been working on and to do so in a way that fits with Django’s philosophy. http://www.stonemind.net/blog/2007/03/15/test-driving-a-restful-django-contribution/

consulting » Test Driving a RESTful Django Contribution

http://duganchen.ca/django-tastypie-and-generic-foreign-keys/

Dugan Chen's Homepage

from django.test import TestCase
http://net.tutsplus.com/tutorials/other/a-beginners-introduction-to-http-and-rest/ Hypertext Transfer Protocol (HTTP) is the life of the web. It’s used every time you transfer a document, or make an AJAX request. But HTTP is surprisingly a relative unknown among some web developers. This introduction will demonstrate how the set of design principles, known as REST, underpin HTTP, and allow you to embrace its fullest power by building interfaces, which can be used from nearly any device or operating system. Republished Tutorial

A Beginner’s Introduction to HTTP and REST

http://joshbohde.com/blog/simple-rest-uris When talking about REST APIs, one of the frequent questions pertains to the benefits of using an Accept header , rather than file extensions, to do content negotiation. Often, the benefits of the Accept header don’t seem to outweigh the familiarity of file extensions. An Example Application Let's say I have a small command line application that prints out issue information from an issue tracker corresponding to a local feature branch in Git.

Simple REST URIs : blog : Josh Bohde

Utiliser une architecture RESTful avec Django — Le blog des développeurs de Pilot Systems

http://bo.blog.pilotsystems.net/2011/juillet/utiliser-architecture-restful-django Cet article introduit les architectures basées sur REST (Representational State Transfer) dans le cadre du développement d'applications Web et d'APIs avec Django ainsi que les problématiques rencontrées avec les méthodes HTTP PUT et DELETE. Qu'est-ce que REST ? Une architecture dite RESTful permet d’identifier des ressources (correspondant classiquement à des modèles ou classes d’objets stockés en base de données) accessibles par l’utilisateur, qu'il soit un être humain ou un système informatique, via des URLs et de modifier leur état via des verbes et paramètres de la requête HTTP invoquant cette URL. Chaque URL est reliée à une fonction (qu’on appelle une "vue" dans Django) capable d’effectuer un traitement sur une requête HTTP, puis de renvoyer une réponse HTTP en fonction du verbe et des paramètres HTTP qu’elle a reçus dans la requête initiale. Chaque application Django contient les vues, modèles et URLs propres à son fonctionnement.

★ Développer une application RESTful avec Django — Biologeek

https://larlet.fr/david/biologeek/archives/20070501-developper-une-application-restful-avec-django/ Après vous avoir expliqué la théorie sur l'architecture REST , rien de vaut un exemple concret pour bien comprendre le mécanisme. J'ai longtemps hésité entre la classique todolist et un agrégateur pour l'exemple mais j'ai finalement opté pour ce dernier en souvenir d' un projet et pour en aider un autre qui va révolutionner votre notion de l'agrégation (ce sont eux qui le disent en tout cas...). Pour commencer un petit avertissement : cet exemple est très basique et ne développe ni toutes les possibilités de REST , ni toutes les fonctionnalités d'un agrégateur.
Summarize a set of RESTful design practices that I have used quite successfully. Object Patterns If there are many objects of the same type, the object URL should contains the id of the object. http://www.xyz.com/library/books/668102

RESTFul Design Patterns

http://horicky.blogspot.com/2009/05/restful-design-patterns.html
http://joshbohde.com/blog/django-backbone-pushstate After working on a few projects with Django and Backbone, I really wanted to replace my hash-driven apps with pushstate . Django-pjax is a library aimed at making this easier for more traditional projects, but would require me to duplicate my display logic server side, without using my current mustache templates. After a few iterations, I've settled on an approach that is DRY enough for my taste. You can view the work in my django-backbone-example project . One way to keep the project keeps templates DRY is through a template tag that renders mustache templates inline .

Using Pushstate with Backbone.js and Django : blog : Josh Bohde

REST Anti-Patterns

http://www.infoq.com/articles/rest-anti-patterns Posted by Stefan Tilkov on Jul 02, 2008 Sections Enterprise Architecture , Architecture & Design Topics
http://blog.programmableweb.com/2010/08/13/api-anti-patterns-how-to-avoid-common-rest-mistakes/

API Anti-Patterns: How to Avoid Common REST Mistakes

Web APIs typically use REST style for communication while moving away from more traditional SOAP web services. Our ProgrammableWeb service directory currently lists around 1500 services which are using REST , and around 360 using SOAP . Why is REST becoming so popular and what are the common mistakes in the REST API design?

REST worst practices

A few weeks ago, I sent the following in a email to a co-worker asking for input on designing REST APIs in Django. Since then, I’ve quoted myself a few times; I thought these thoughts would be worth a (slightly edited) public home. I think the best way to dive in terms of mistakes to avoid. If you poke around you’ll find a couple-three different stabs at writing a generic REST API module for Django.

Refactor the Life » Blog Archive » RESTful Django practice

After several rounds reading RESTfull Web Services , I still have feeble confidence on my understanding the hyped REST idea, so please never hesitate to criticize, suggest in the comment. A book can be easily be identified by ISBN or EAN, however, it may stand for the specific book other than other books, or it refers an eBook instance to for content presentation. We use an additional argument, format to differentiate them: /bookshelf/books/(isbn|ean)?

A Django Anti-Pattern, Rolling Your Own REST

Last week I got an email from Charlie O'Keefe , and one of the topics it hit upon was the lack of simple support for RESTful apis in Django. I promised a quick blog entry on the topic, but it hasn't really been coming together. The problem is one of a library. Not that there aren't libraries, there are a handful, but none of them have quite hit the sweet spot yet. I think that the community hasn't been too bothered by this lack because its usually trivial to write the RESTful view you need by hand using just a couple of views.