By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,905 Members | 1,783 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,905 IT Pros & Developers. It's quick & easy.

How do I prevent new window from sharing session vars?

P: n/a
Guy
Is there a way to prevent new browsers windows from sharing session
variables with the original window?

Our team has an ASP.Net app that lets users analyze portfolio risk
given certain portfolio constructions. The set weights to certain
asset types, hit calculate and see some results. Our problem is that
users want to compare different situations side by side. So they
either hit CTRL+N or Choose "File, New" launch a new browser window,
change their inputs and recalculate. Change things some more and hit
calculate again. But since they spawned Window 2 from Window 1, and
we store the inputs in session variables, the new inputs from Window 2
show up in the calcs for Window 1. Is there anyway around this?

We have too much data to store on the querystring by the way.
Guy
Nov 19 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Guy,

You are out of luck here. New session involves a new process, and you cannot
launch a new process unless you have elevated scripting privs.

It may be slow, but consider going with ViewState instead.

-- Alex Papadimoulis

"Guy" wrote:
Is there a way to prevent new browsers windows from sharing session
variables with the original window?

Our team has an ASP.Net app that lets users analyze portfolio risk
given certain portfolio constructions. The set weights to certain
asset types, hit calculate and see some results. Our problem is that
users want to compare different situations side by side. So they
either hit CTRL+N or Choose "File, New" launch a new browser window,
change their inputs and recalculate. Change things some more and hit
calculate again. But since they spawned Window 2 from Window 1, and
we store the inputs in session variables, the new inputs from Window 2
show up in the calcs for Window 1. Is there anyway around this?

We have too much data to store on the querystring by the way.
Guy

Nov 19 '05 #2

P: n/a
you should always design for this case. use a transaction guid to track a
set of session values. on postback lookup the values for the transaction
guid in the postback (you might want to use sqlsessions to reduce memory
load).

-- bruce (sqlwork.com)


"Guy" <su*****@yahoo.com> wrote in message
news:df**************************@posting.google.c om...
| Is there a way to prevent new browsers windows from sharing session
| variables with the original window?
|
| Our team has an ASP.Net app that lets users analyze portfolio risk
| given certain portfolio constructions. The set weights to certain
| asset types, hit calculate and see some results. Our problem is that
| users want to compare different situations side by side. So they
| either hit CTRL+N or Choose "File, New" launch a new browser window,
| change their inputs and recalculate. Change things some more and hit
| calculate again. But since they spawned Window 2 from Window 1, and
| we store the inputs in session variables, the new inputs from Window 2
| show up in the calcs for Window 1. Is there anyway around this?
|
| We have too much data to store on the querystring by the way.
|
|
| Guy
Nov 19 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.