Hi Ben, Memcache is global to your app. It has no relation to the protocol the user used to access it. The issue you're seeing is undoubtedly due to something else - possibly memcache just expiring data, as it's allowed to do at any time!
-Nick Johnson On Fri, Jun 18, 2010 at 11:50 AM, BenF <[email protected]> wrote: > I had been trying to use memcache for holding session information. > However, I found that when a Memcache value is set by the app in > response to a secure (https)connection from the client, that value is > not visible when the app has been accessed a few seconds later using a > standard connection (http). > > I haven't done any specific tests to check whether that is really true > - just in the tests of my app, I failed to get the session continuity > working using memcache and I resorted to keeping that data in the > datastore instead. > > It would be nice to know though, is memcache data partitioned > according to whether the connection is https or http? > > -- > 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]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- Nick Johnson, Developer Programs Engineer, App Engine Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: 368047 Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: 368047 -- 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.
