On Mar 17, 10:45 pm, Jacob Kaplan-Moss <jacob.kaplanm...@gmail.com> wrote: > On Tue, Mar 17, 2009 at 8:55 PM, Huuuze <huu...@ymail.com> wrote: > > 7. Django detects the missing cookie > > I think this is where you're getting hung up. Django doesn't "detect" > a "missing" cookie; Django sees a request from a browser that doesn't > include a cookie. Nothing's missing; it's just a new browser without a > cookie. > > To Django, there's *no difference* between a user browsing a site > until his cookie expires then coming back, and the same user browsing > until the cookie expires and then a *second* user visiting without a > cookie. There's no "I used to have a cookie but now I don't" header; > there's either a session cookie, or there isn't. > > Huuuze, I can appreciate that this is an infuriating aspect of HTTP -- > statelessness is a real bitch sometimes. But you need to accept that > you're asking the impossible here and move on.
Jacob, as you can see in my previous post (where I stated "And I agree with you: I don't think this can be done..."), I have moved on. There is no need for the condescending tone in your previous post and lest we forget this is a *support* group. I do understand the limitations and, in the case of my description of Step 7, I simply chose the wrong words. Regardless, thank you again for assisting and setting me on the right path. > > Jacob --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
