On Wed, 2009-01-21 at 05:23 -0800, Iqbal Abdullah wrote: > Hi Malcolm, > > Thank you for the tip! > I see now that in my particular code example above, the idea of using > session id and manually setting it through the request can only work > if the session id itself doesn't change after i've set it into the > response. From your explaination, there is no guarantee of this > happening, so in the code above I've to make sure that the timing of > setting it into the response must be the last action before passing it > to render_to_response() > > Please point out if my logic is mistaken.
I must admit that I don't really understand what you're trying to do here. However, I would strongly suggest simply following the same logic as the existing session middleware, which seems to involve setting things at the last minute. Personally, though, if I had to work on a system that didn't allow cookies, I'd try to avoid using Django's session framework. You don't need sessions very much in many situations (the usual amount is to record that somebody is logged in and an encrypted form variable of URL parameter could do that), so you might be trying to solve a small problem with a large and awkward hammer. In any case, good luck. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
