Changes between Version 3 and Version 4 of ClassBasedViews

Timestamp:

Oct 1, 2010, 10:32:32 AM (14 years ago)

Author:

Carl Meyer

Comment:

add "store state on request" thread-safety option

ClassBasedViews

@@ -27 +27 @@
 === 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.
+
+==== Store state on request, not view ====
+
+Pass around the request object via method arguments, store arbitrary state on the request (perhaps in a blessed dictionary for that, or just in attributes). Document that state should be stored on the request, storing it on the view instance is unsafe, just like is already the case with ModelAdmin subclasses.
+
+Example usage and view would be the same as shown below in "__call__ and copy()".
+
+Arguments for:
+ * Avoids messy and non-idiomatic hacks.
+ * Avoids copying or creating new view instance on every request.
+
+Arguments against:
+ * Leaves some room for people to shoot themselves in the foot.
 
 ==== !__call!__() and copy() ====