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 for determining a solution will come from this issue on the appengine SDK google code project. http://code.google.com/p/googleappengine/issues/detail?id=732 On Nov 18, 9:44 am, Michael <[EMAIL PROTECTED]> wrote: > 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 "Google App Engine" 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/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
