Tuesday, August 31, 2004 Hi Aparajita,
> Table-based sessions are no longer supported Aha! Glad I asked (before wondering why it didn't work after building it... :-). As I mentioned, I downloaded both the Demo files as well as the Plugin; I found this parameter (I think) in the Demo version of Active4D.ini. Is there a "definitive" version of the Active4D.ini file (just so I don't accidentally start using some parameter that's not supported)? (I see you did mention that the "session cache mode" option has been removed in the Release notes, but as I mentioned, I'm new, so I didn't quite pick up on that when I first read the docs and then later started tackling this issue.) > If you want to save a > session across a restart, you will have to use 'session to blob', save > it, then 'blob to session' to restore it. Hmm, sounds like a suitable replacement strategy. Question: as you mention, Active4D gracefully destroys any active session when the database is being shut down. However, if the user is on a page when this happens (hasn't hit the SUBMIT button or navigate a link), is their session (in their cookie on their computer) still valid? That is, once the site comes back up, and I restore their session from the blob (which should have the same session ID as their cookie?), the next page they submit will work correctly (as if the site didn't go down)? I think the answer is yes, but want to make sure I'm understanding it correctly. In the end, however, it might just be easier (at least until people complain) to just force them to log back in and start over. I sense it's going to be a strange to try to maintain a session over a restart: is the web user going to have the patience to stick around waiting for the site to come back on line (staring at a spinning beach ball or whatever)? Probably not. Even though it might be down for just a few minutes, most users would assume something's not working right, give up, and try again later (when their session would be expired anyway). The site is initially going to be used mainly for reference (looking stuff up); there are a few forms to fill out as well, but as you said, it might be best to try to do the structure updates at a period of low activity and not too frequently (although I don't have any control over that, as code changes come whenever required and with whatever urgency they may have). Thanks for your help! Sure is great to get to speak with the original developer!!! > Make sure you come to my fusebox session! Looking forward to it! Cheers! Michael Larue _______________________________________________ Active4D-dev mailing list [EMAIL PROTECTED] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
