I don't have a code sample, but you would need to create a custom session handler with session_set_save_handler() <http://php.net/manual/en/function.session-set-save-handler.php> as per the suggestion provided in this post <http://stackoverflow.com/questions/20272634/storing-session-data-in-database-and-memcache> on Stack Overflow.
On Monday, January 25, 2016 at 3:36:59 PM UTC-5, Alex Kerr wrote: > > Hi, > I'm using standard PHP session stuff for my web app, which means session > data is stored in App Engine's shared memcache. Google's docs state that > this can get flushed so any logged in user sessions would fail. How exactly > do I add use of Datastore (or Cloud Storage?) into this process so that > memcache is still used unless it gets flushed in which case Datastore is > referred to? Is there a way to do this that minimises Datastore reads & > writes and thus minimises cost and latency? I'm ideally after code (or even > pseudocode) or even better a drop-in library or class :) > > Or, is a flush of the shared memcache so unlikely that it doesn't really > matter? > > Many thanks. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/4d97d85e-5875-4773-a0b5-5aaff5dfed9b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
