But if you want reliable persistance you are going to have to store it in the DB at some stage anyway.
And why not store it AND put it in the session each time you create a new session? On Wed, 21 Mar 2007 16:51:27 -0000, Amit Upadhyay <[EMAIL PROTECTED]> wrote: > On 3/21/07, Michael Radziej <[EMAIL PROTECTED]> wrote: >> >> On Wed, Mar 21, Amit Upadhyay wrote: >> >> > Hi, >> > >> > Django has anonymous sessions, tracked by cookies. The session can not >> be >> > accessed from a different machine for the same user >> >> What do you mean with 'accessed from a different machine'? Another >> server >> (in a load balancer or similar), or another client? Both isn't true. > > > I mean from a different client/browser. > > >> which drastically >> > reduces the usefulness of sessions. Another approach to save something >> > persistently for a user it to update the UserProfile model and create >> a >> new >> > row for the same, but this will require altering the corresponding >> table >> > every time we realize we have one more thing to save. >> >> I probably simply don't get what you try to do. Can you give an example, >> please? > > > I have for example, lots of notifications to users, like show popup for > this > and show popup for that. The thing is user may not be interested in a > lot of > these popups [consider firefox's message: you are about to submit a data > on > unencrypted connection, are you want to proceed?"] and we want to put a > checkbox in those dialog's saying "do not show this message again". I > want > to store this information somewhere, and currently I am doing it in > UserProfile model of mine, but as things keep on getting added it becomes > more unwieldy. Putting everything in a separate model removes the > context of > each settings, and makes documentation difficult, while if things are in > sessions, only a set of views responsible for the given page on which we > are > showing the popup, and ajax handlers for it, will have to know about > settings related to that page. No need to alter tables. > > Session is the right place for a lot of these things, (for if not, what > is > session suitable for?) but the current django session is not persistent, > which leads to my this request. > -- http://belfast.no-ip.info/ Get http://www.ubuntu.com/ --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
