On 4/18/07, James Bennett <[EMAIL PROTECTED]> wrote: > > On 4/18/07, SlavaSh <[EMAIL PROTECTED]> wrote: > > This is wrong "intentional design decision". > > There few more web clients in the world besides the IE and Firefox. > > Part of them does not support cookies. > > Django provides a sessions framework in 'django.contrib.sessions' > (note the "contrib" in that path) as a convenience for the common case > of needing to persist state across multiple HTTP requests. The common > case involves a user-agent which is capable of handling cookies -- > around 90% of all web clients have cookies enabled, and the percentage > which does not tends to include fairly specific demographics and so > are not a problem for most sites > > For the uncommon case, it would be possible for you to write your own > wrapper around the sessions framework which uses some other mechanism, > but I think this is a case where we simply will not be able to please > everyone with what Django ships by default, so we need to stick to > meeting the needs of the common case.
besides: wc -l * 0 __init__.py 103 middleware.py 88 models.py 191 total its just a few lines of code, just write your own middleware that will handle session_id's in URL. You can still use the API and the models from django.contrib.sessions... > > -- > "Bureaucrat Conrad, you are technically correct -- the best kind of correct." > > > > -- Honza Kr�l E-Mail: [EMAIL PROTECTED] ICQ#: 107471613 Phone: +420 606 678585 --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
