The best way to really understand sessions is to understand some of the underlying HTTP transport and the issues involved with simulating stateful client->server interactions over a stateless protocol. Might sound complicated but it really isn't.

Although django makes it easy to build apps without understanding some of the HTTP mechanics involved, it really does help you write better code to understand the underpinnings, I think.

RFC 2109 is a good starting point if you're comfortable with RFCs

Otherwise the wikipedia entry for HTTP cookie is a good overview that describes managing cookies (like django's session framework) and some of the alternatives people use, both good, and profoundly silly.

One of the classic "Gotchas" of session programming (and web programming in general) is making assumptions that won't work in a load balanced multiple webserver environment. Django gets around this by storing sessions in the database, which is a bit of a mixed blessing IMHO.

Cheers,
~ol

On 10/25/06, Darryl Caldwell <[EMAIL PROTECTED]> wrote:
Hi all,

I like the django session programming framework, but I would like a general (not just django) understanding of session programming do's and don'ts. Does anyone have any pointers to documents? Thanks.

-Darryl





--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to