Hi Sameer, Doing a StructClear() on the session scope only deletes your session variables. The cookie variable jsessionid will still exist and still point to an empty session scope structure. Creating a new session variable and calling it sessionid makes no difference - it's a separate variable.
So to answer your questions: 1.> Any reliable way of getting/keeping sessionid Use cookie.jsessionid 2.> What happens to session.sessionid on timeout. How is it recreated. This variable isn't the session identifier, just one you created. I'll assume you're really asking what happens to cookie.jsessionid. It disappears on timeout. However, a new cookie.jsessionid will be created automatically the first time you run a page with <cfapplication sessionmanagement="yes" ...> in it (or in Application.cfm) 3.> Is there any better way to force a new session on a different window. If the new window is a separate application, give the application a different name in the cfapplication tag. That way, you'll always have separate session scopes. HTH Tim --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
