On 10/17/11 1:42 PM, neurino wrote:
Reading one more time Michael mail about the recipe:
> It advocates a mechanism to query the user the first time you access
that property of the request object and cache the result in memory for
the lifetime of that request
*That's right the way I wanted it to work!*
So why if I reload a page my user is not queried again and stills to an
older state?
Um, is it possible that you're just getting the same page from your
browser cache, and therefore you're not hitting your server at all?
Have you tried shift-reload to see if that changes the behaviour?
-r
I *don't want* at all to have session variables, I want a brand new
queried request.user attribute each time the user loads its profile page.
Thanks for your support
neurino
On Mon, Oct 17, 2011 at 7:24 PM, Michael Merickel <[email protected]
<mailto:[email protected]>> wrote:
It advocates a mechanism to query the user the first time you access
that property of the request object and cache the result in memory
for the lifetime of that request
--
You received this message because you are subscribed to the Google
Groups "pylons-discuss" 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/pylons-discuss?hl=en.
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" 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/pylons-discuss?hl=en.
