Since I'm focused on the webserver today, I'm coming back to not being clear on the distinction 4D makes between a 'web session' and the 'web process' when using automatic session management.
A web session, as I understand it, is an authorized connection between a browser and the server and usually designated with a cookie. 4D uses the 4DSID cookie and there's a database param that let's me set the cookie timeout period. When a new connection is made from a browser 4D looks for the cookie and if it's there looks for a web process with that session id. If it finds a process it should use it, if it doesn't (and the cookie is still valid) it starts a new process which should have that session ID assigned to it. But that's not the way I see it actually work. A new process spins up each time new request comes in and gets assigned a new web session id which replaces whatever the 4DSID cookie is. So I've got the feeling I'm not using the automatic session features the way they should be - or it's something else. Again, comments from folks doing more of this stuff are much appreciated. Kirk Brooks San Francisco, CA ======================= *The only thing necessary for the triumph of evil is for good men to do nothing.* *- Edmund Burke* ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
