Keeping a session in a database accessible to all
applications might help. On the browser side you
can keep an encrypted cookie with a session
identifier. The identifier might have IP address and
browser agent MD5'd to reduce man-in-the-middle
hijack attempts. On your side, keep whatever you
need in the database - including pickled objects.
James
On Oct 25, 12:35 am, "Mike Orr" <[EMAIL PROTECTED]> wrote:
> I have two sites I want to convert to Pylons...
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
