Jeremy Dunck wrote:
>
> The attached file implements a (lightly-tested) middleware.
Wow, thanks a lot!
I'll let you know how it goes!
- bram
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group
On 1/23/07, Will McCutchen <[EMAIL PROTECTED]> wrote:
...
> I would add option #5: Write a custom middleware component to update a
> last_accessed attribute for logged in users on every request.
>
> http://www.djangobook.com/en/beta/chapter16/
If you have a lot of requests, I doubt you really wan
On Jan 23, 1:18 pm, "Rob Hudson" <[EMAIL PROTECTED]> wrote:
> I don't have an answer but some thoughts...
Me, too...
> I'd probably go with the 3rd option. But if that didn't work, maybe
> look at writing my own session middleware that added new column to the
> django_session table that was a
I don't have an answer but some thoughts...
1) last_login isn't on by default. That's actually an unasked question
I've had -- are there examples that show this working?
2) last_login would presumably be set only on login, not on every
request. So this wouldn't be the field to use for this any
hey everyone,
haven't seen any hacks around, so thought I'd better ask...
is there a way to get the "currently online users" in some way?
Something like: "if a user has done something in the last 2 minutes he's
considered online".
Or is this exactly what
5 matches
Mail list logo
