GSoC 2007 Status Update IV: Django REST interface - Django developers

Message from discussion GSoC 2007 Status Update IV: Django REST interface

David Larlet

More options Aug 6 2007, 4:08 am

From: "David Larlet" <lar...@gmail.com>

Date: Mon, 6 Aug 2007 10:08:54 +0200

Local: Mon, Aug 6 2007 4:08 am

Subject: Re: GSoC 2007 Status Update IV: Django REST interface

  Reply to author
  |
  Forward
  | Print
  | View thread
  | Show original
  | Report this message
  | Find messages by this author
  

2007/8/3, Andreas Stuhlmüller <stuhlmuel...@gmail.com>:

> On 7/13/07, David Larlet <lar...@gmail.com> wrote:
> > * About users, how can I handle django users' permissions? John
> > Sutherland had already done some work on django-crudapi [1] and it
> > could be interesting to allow this access control.

> Good question. I would subclass one of the authentication classes,
> e.g. HttpBasicAuthentication, and add a has_perm() check dependent on
> the request method to is_authenticated().

> Currently, REST authentication is independent from Django's
> authentication middleware. It might make sense to move most of the
> code in HttpBasicAuthentication and HttpDigestAuthentication to
> django.contrib.auth.backends and to let the middleware do most of the
> work.

Sounds good to me.

> > I'm not fond of CRUD names and I prefer to keep an information on
> > the HTTP verb in the function name but it's maybe personal.

> I chose the CRUD names as they better describe what the methods
> actually do, but if the consensus is that it is more important to
> highlight the HTTP method, I will change this.

Eventually, I'm not against CRUD names but maybe we could be
consistent with rails ones?

> Thanks for your comments!

Thanks for your answer :)

Regards,
David

Reply to author Forward