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 what you say request.user needs to be done on every request why is it not design to put it in the session ... instead of request.user it should be request.session['user'] ... although request.user is much code friendly, I just want to understand how django works for me to learn this framework well. Isn't session will be done only if there's a change in it? assumming we define SESSION_SAVE_EVERY_REQUEST = False Thanks james --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
