>>I don't know what you mean by Member.Session (?) but yes, ASP.NET session.
>
>The Member.Session field is a framework related field I am using to recognize the user from a stored cookie. That is initialized at login.
>
>>Yes. If you allow sessionId to be stored in a cookie you will get the same id for new instances (or new tabs) for the relevant browser.
>>If 'cookieless=true' the session id is included in the URL and you get a different session for each instance or tab.
>
>Is this something you have to maintain on your own or this is all automatic?


PMFJI, It is mostly automatic, but I had some cases where I was building URL at runtime that required a call to Response.ApplyAppPathModifier to add the session ID to the virtual path.