Changes between Version 11 and Version 12 of ClassBasedViews

Timestamp:

Oct 12, 2010, 1:02:19 PM (14 years ago)

Author:

Luke Plant

Comment:

--

ClassBasedViews

@@ -26 +26 @@
 
 === View instantiation and thread safety ===
-The [http://groups.google.com/group/django-developers/browse_thread/thread/e23d9a5a58fe5891 most recent django-developers discussion on the topic] discussed many of the available options on instantiating the views and protecting them from threading issues. Here is a summary of the various approaches that have been proposed.
+The [http://groups.google.com/group/django-developers/browse_thread/thread/27cec79b784ef73f?hl=en1 most recent django-developers discussion on the topic], and [http://groups.google.com/group/django-developers/browse_thread/thread/e23d9a5a58fe589 an older thread] discussed many of the available options on instantiating the views and protecting them from threading issues. Here is a summary of the various approaches that have been proposed.
+
+Some examples showing the essence of each of them without the other details:  http://bitbucket.org/spookylukey/django-class-views-experiments/src/tip/
 
 ==== Store state on request, not view ====
@@ -128 +130 @@
 Arguments against:
  * The URLconf is slightly more verbose
+ * If you do `AuthorDetail(foo=True).as_view()`, instead of `AuthorDetail.as_view(foo=True)`, you will not get an exception, but `foo=True` will effectively be ignored.
 
 
@@ -151 +154 @@
 ==== Recommendation ====
 
-Based on these discussions, plus in-person discussions at !DjangoCon.eu,  `__copy__()` on `__call__()` appears to be a slight front runner, with `__new__()` as a close runner up.
+Based on these discussions, classmethod2 appears to be the winner.
 
 === Class Hierarchy ===