Thanks, I'm looking forward to hearing from you.
This however still leaves me with the question: is this the way I am
supposed to handle an OpenID logged user?
Best,
Michael
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
In short, I believe session management is the best way to do that,
yes. I'm hoping to wrap up the part of my project I'm working on
sometime next week when I have some time. After that, I'll be tackling
this issue myself. Not for OpenID (yet), but for oauth login sources
like Google, Yahoo, and
What browser are you checking with? I've had some problems with IE
ignoring the cache-control headers. Do you get the same results in
firefox? I just checked the gaeutilities demo, and it's session demo
isn't working either, again. I'll take a look at this as soon as I
can.
On Nov 17, 4:02 pm,
Hi,
It fails in Firefox 3, IE 6 and Chrome 0.3.154. However Chrome seems
to handle it slightly better (sometimes the session is immediately up
to date).
Regards,
Michael
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
It must still be a caching issue due to appengine. I'm hesitant to
modify headers directly in the session class, however I'll look into
trying to figure what's necessary to get it to work and document it.
I'm not sure if I'll have time to look at this before next week.
The best starting point
