From 7e5d522674b0d80995102847e82efdbdcbbb7803 Mon Sep 17 00:00:00 2001
From: mjumbewu <mjumbewu@gmail.com>
Date: Sat, 8 Sep 2012 08:22:13 -0700
Subject: [PATCH] Updated DjangoCon US 2012 Sprints (markdown)

---
 DjangoCon-US-2012-Sprints.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/DjangoCon-US-2012-Sprints.md b/DjangoCon-US-2012-Sprints.md
index 08002cb..6e13131 100644
--- a/DjangoCon-US-2012-Sprints.md
+++ b/DjangoCon-US-2012-Sprints.md
@@ -71,6 +71,8 @@ Resources are view-like classes that implement everything except the actual `.ge
 
 I think the base ModelResource will probably need to be composed of `APIView` Django's `MultipleObjectMixin` *and* `SingleObjectMixin`, plus *all* the REST framework mixins. 
 
+> Maybe instead it can just be derived from `object`, and act as a mixin itself.  Then, the routers would just construct classes that derive from the appropriate mixins as needed. - @mjumbewu
+
 ### Test out object-level permissions.
 
 REST framework should now support object level permissions.  (See `SingleObjectBaseView.get_object()` in `generics.py`.)  Using a view with `DjangoModelPermissions`, install `django-guardian` and see if you can get everything playing together nicely.  If so, the Authentication documentation should be updated to reflect that.