That's good news. Here's what I think is happening: - GAE uses the datastore to hold session data; it appears to be optimized to only write to the datastore when session data has changed. - CFML session data for unnamed applications is written directly to the session scope; therefore, GAE sees the changes to session variables and writes them to the datastore. - For CFML named applications, session data is stored in a CFML struct variable which is stored in the session scope (the key is the application name). Because BD only writes to the CFML struct, GAE doesn't see changes to session variables and doesn't write to the datastore.
Assuming the above is correct, the fix is going to be for BD to re-write the CFML struct to the GAE session scope when it know there were changes. I'll open a bug report to track this. Thanks for your patience and persistence in pursuing this issue. Vince On Fri, May 7, 2010 at 1:58 AM, Adam Knott <[email protected]> wrote: > Thanks Vince, > > Using an unnamed application works. Sessions seem to be behaving as > expected. I can see _ah_sessions in the datastore and sessions live > between application deployments to appengine, so I think that may be > an indication that sessions would work across a cluster. Thanks for > all your help. > > Adam > > -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon mailing list - http://groups.google.com/group/openbd?hl=en !! save a network - please trim replies before posting !!
