Re: understanding request.user

On Aug 1, 9:25 pm, james_027 <[EMAIL PROTECTED]> wrote: > hi, > > ... I just want to understand how > django works for me to learn this framework well. My guess as to the intent of the design is that caching a database backed object in the session wouldn't be a good idea as it can get out of sync

Re: understanding request.user

hi, > request.user gets created by to OR mapping (from the sql database). > request.session comes from a pickle (serialized to a bytestream). > > Both needs to be done for every request. You could use caching, > but object caching (like for request.user) is not possible up to now. > Just like w

Re: understanding request.user

Am Mittwoch, 1. August 2007 10:23 schrieb james_027: > hi, > > I am seeking some enlightenment as why the user (variable use to track > if the user is logged in or not) seems to be on the request level and > not on the session which is the practice of most or all of web > framework? If I am not wr

understanding request.user

hi, I am seeking some enlightenment as why the user (variable use to track if the user is logged in or not) seems to be on the request level and not on the session which is the practice of most or all of web framework? If I am not wrong request.user is done on the middleware which will get execut