On 3/21/07, Michael Radziej <[EMAIL PROTECTED]> wrote:
>
...
> If you find altering the database tables is a problem, you could use a user
class User(...
class Message(...
class UserMessagePref(...):
user = FK(User)
message = FK(Message)
muted = Boolean()
No? Or is it that you don'
On Wed, Mar 21, Amit Upadhyay 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 u
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 -, Amit Upadhyay <[EMAIL PROTECTED]>
wrote:
> On 3/21/07, Michael Radz
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
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 c
Hi,
Django has anonymous sessions, tracked by cookies. The session can not be
accessed from a different machine for the same user, 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
ro
