Doing REST with django, part 1 - research
The django framework provides no best practice for implementing a REST API. Part one of these series will therefore consist in trying to find out which approach suits our purposes + which resources are already available.
Articles
Some articles on REST and django:
Some Existing Projects
1. django-rest-interface
The result of a GS0C project, project seems in a coma. The design looks good, along the lines of what I was thinking. Implementation is limited however, more like a prototype than a real world library.
2. piston
Piston is a Django mini-framework creating APIs, originally written for bitbucket. Design looks good, very integrated with django.
3. multiresponse
Small library for Django to provide mime type aware responses. This allows a client to receive different responses based on the HTTP "Accept" header they send. This is used in place of ``render_to_response`` or a manual``HttpResponse``.
Articles
Some articles on REST and django:
- Blog post by Viktor Nagy : what existing django-rest library to use for his specific purposes.
- REST worst practices by Jacob Kaplan-Moss
- ETags, Content Types support in django
Some Existing Projects
1. django-rest-interface
The result of a GS0C project, project seems in a coma. The design looks good, along the lines of what I was thinking. Implementation is limited however, more like a prototype than a real world library.
2. piston
Piston is a Django mini-framework creating APIs, originally written for bitbucket. Design looks good, very integrated with django.
3. multiresponse
Small library for Django to provide mime type aware responses. This allows a client to receive different responses based on the HTTP "Accept" header they send. This is used in place of ``render_to_response`` or a manual``HttpResponse``.
Comments