Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
GSoC 2007 Status Update II: Django REST interface
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Andreas Stuhlmüller  
View profile  
 More options Jun 9 2007, 7:13 am
From: "Andreas Stuhlmüller" <stuhlmuel...@gmail.com>
Date: Sat, 9 Jun 2007 13:13:42 +0200
Local: Sat, Jun 9 2007 7:13 am
Subject: GSoC 2007 Status Update II: Django REST interface
This is the second weekly status update for my Summer of Code project,
a generic REST interface for Django [1].

This week, I was mostly working on improving the architecture of the
code, in particular by splitting ModelResource into two classes,
Collection (for querysets) and Entry (for individual models). Other
improvements include appropriate HTTP status codes for POST/PUT
requests, the option to use templates for the response formatting
(TemplateResponder), basic pagination (works both with serialized and
templated output) and load_put_and_files, a function that populates
request.PUT and request.FILES via _load_post_and_files.

Compared to my initial timetable, I am in time. Looking at my last
status report, I notice that error handling isn't perfect yet (needs
to be unified) and the option to limit the model fields exposed by the
API and the inclusion of resource URIs in serialized output are not
done yet.

The main thing I will do next week is to think about and improve
automated URL generation.

I am still working on the first part of my proposal (resources that
correspond directly to models). If you have any thoughts on what
should or should not be possible with such a REST API or if you have
specific comments on the code, please let me know.

Regards,
Andreas

[1] http://code.google.com/p/django-rest-interface/


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »