-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/09/2012 09:01 AM, Carl Meyer wrote: > This is not an option because the database session backend is only one > of many session backends.
Oh, never mind - I misunderstood the proposal. This wouldn't be dependent on using the database session backend if its done entirely in the auth app and based on the session key. It would, however, require a database check on every session access, meaning the value of using a faster session backend would be lost. Thus I still think it's not feasible, and (if anything is to be done here) a solution like #3 that stores extra data in the session itself is preferable. Carl -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8LEGQACgkQ8W4rlRKtE2faiwCfUhQg9MouUnkGpYWec7WI1VJL C7UAnjgEIiAgruPSPnlEZfucyRWmxbV3 =Jpx9 -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
