On 12/6/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Hrm if that's the case, I msut have slipped up in the code somewhere.
> Thanks :)
>
> I'll go see if i am inserting into sessions for some reason if they're
> anonymous.
To aid in things like this, I used a modded version of sessions wh
Hrm if that's the case, I msut have slipped up in the code somewhere.
Thanks :)
I'll go see if i am inserting into sessions for some reason if they're
anonymous.
On Dec 6, 4:27 pm, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > It is a problem. It hits the db if it has t
[EMAIL PROTECTED] wrote:
> It is a problem. It hits the db if it has to create it.
Sorry I still don't understand :-). You say that you do need
authentication but don't need anonymous sessions. Then in default Django
setup you never hit a database unless you try to store something in
session.
It is a problem. It hits the db if it has to create it. If i have to
I'll rewrite the library.
On Dec 6, 12:31 pm, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > Well we obviously need authentication, we just don't need anonymous
> > session handling.Then it shouldn't be
[EMAIL PROTECTED] wrote:
> Well we obviously need authentication, we just don't need anonymous
> session handling.
Then it shouldn't be a problem. Sessions are created and hit db only if
you store something in it. Or if you have SESSION_SAVE_EVERY_REQUEST =
True. Otherwise request.session is ju
Well we obviously need authentication, we just don't need anonymous
session handling.
On Dec 6, 11:31 am, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > I'd like a simple option to disable this, any plans to implement
> > something of the sorts?The intended way is to remo
[EMAIL PROTECTED] wrote:
> I'd like a simple option to disable this, any plans to implement
> something of the sorts?
The intended way is to remove SessionMiddleware and those depending on
it (AuthenticationMiddleware) from MIDDLEWARE_CLASSES and
'django.contrib.sessions', 'django.contrib.auth'
Unfortunately the whole thing seemed to cause the "User tampered with
cookie" error. I'm not sure why, or how, but storing the results
seemed to create the erorr.
O well.
On 11/18/05, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> On 11/16/05, Brant Harris <[EMAIL PROTECTED]> wrote:
> > Is
On 11/16/05, Brant Harris <[EMAIL PROTECTED]> wrote:
> Is it wise to store a large amount of data in an anonymous session?
> For instance, and most applicable to my design, if I store results of
> a search in a session like so:
> request.session['search_results'] = objects.get_list(name__icontains
9 matches
Mail list logo
