John, OK, I see where I was getting mixed up. The session timeout can be a different length than the process timeout. But in practice the session ceases to persist on 4D unless it's active in a process. So when the process providing the context for the session expires that 'session id' goes too. But it's saved in the cookie and so it's on me to get that cookie early on and restore the context if I care about it.
I was thinking 4D would maintain the session id for the duration of the session timeout even if the process the session was running in quit. I see now the session time out is a property of the cookie on the browser and nothing more involved within 4D. When I read through the 'Web Sessions Management' page just now I get what they are saying. The way I read it before I just didn't fully grasp these distinctions. Things are always so much simpler when you understand them. Thanks for the help. -- 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:[email protected] **********************************************************************
