> I guess you could say, "An application where those
> footing the bill (Client) demand it". But, it's not
> application specific, and it's not multiple sessions
> we're talking about here, it's multiple browsers on
> the same session. Multiple sessions are a non-issue.
> Regardless of what your application is, one of the
> following should be true:
>
> 1) You do nothing about multiple browsers on the
> same session, and
> a) You use no session data
> b) You take your chances that session data may
> become corrupt
> 2) You prevent multiple browsers on the same session
> through
> a) JavaScript (Risky, since it could be turned
> off)
> b) Synchronized Tokens?
> 3) You do something to segregate the session data
> between browsers.
4) you configure MSIE not to open new browsers on
the same session. This works, if the application
is being used within a corporate (Intranet)
envinronment.
-TPP
-----------------------------------------
This email may contain confidential and privileged material for the sole use of the
intended recipient(s). Any review, use, retention, distribution or disclosure by
others is strictly prohibited. If you are not the intended recipient (or authorized to
receive for the recipient), please contact the sender by reply email and delete all
copies of this message. Also, email is susceptible to data corruption, interception,
tampering, unauthorized amendment and viruses. We only send and receive emails on the
basis that we are not liable for any such corruption, interception, tampering,
amendment or viruses or any consequence thereof.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
