Can I share Session variables across Applications?

[George Hester]

In one Application (2) the client is redirected to a Logon ASP in a different Application (1). A Session Variable is made in Application 2 which needs to be recognized in Application 1. Can I do that in Windows 2000 SP3 IIS5 no .NET Framework? Thanks.

 

[Aaron [SQL Server MVP]]

No.

http://www.aspfaq.com/2157

--
http://www.aspfaq.com/
(Reverse address to reply.)




In one Application (2) the client is redirected to a Logon ASP in a
different Application (1). A Session Variable is made in Application 2
which needs to be recognized in Application 1. Can I do that in Windows
2000 SP3 IIS5 no .NET Framework? Thanks.

 

[Dave Anderson]

In one Application (2) the client is redirected to a Logon ASP in a
different Application (1). A Session Variable is made in Application
2 which needs to be recognized in Application 1. Can I do that in
Windows 2000 SP3 IIS5 no .NET Framework? Thanks.

Yes, if you use your own session architecture and store the contents of the
variables in a DB.

I have session variables that span applications and servers inside our
domain -- including IIS4/5/6, Apache, and Tomcat servers.



--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms. Please do not contact
me directly or ask me to contact you directly for assistance. If your
question is worth asking, it's worth posting.

 

[Patrice]

What do you want to share ?

By nature, session variables are intendent to store session specific
information for a particular application. If you tell us what you try to do,
someone could come up with a better architecture suggestion.

Patrice

--

"George Hester" <[email protected]> a écrit dans le message de
In one Application (2) the client is redirected to a Logon ASP in a
different Application (1). A Session Variable is made in Application 2
which needs to be recognized in Application 1. Can I do that in Windows
2000 SP3 IIS5 no .NET Framework? Thanks.

 

[George Hester]

Thanks for cart.zip. I saw after this post this was the way to go. Trouble is I am finding that different Applications are not not necessary for this issue to happen. Consider this:

The root is a FrontPage 2000 Sever Extended web. Application 2 is also a FrontPage 2000 Server Extended Virtual Directory of Application 1. In Application 2 there is a ASP with this in it:

<img src="/images/spacer.gif">
<img src="/images/adobelogo.gif">

The first fails while the second one succeeds.

I haven't been able to track down that anomoly yet. Application 2 has an images folder so I just stuck the spacer.gif in there and left the HTML alone. That fixed it.

I know this isn't a Session issue but the ability to "share" across Applications seems to be hazardous.

 

[George Hester]

Yes I was hoping that. This is just a way for determing if Cookies are enabled. The accessed page (In Application 2) sends the client to a logon page (in Application 1) if they don't have a Session not necessarily made in Application 2. The logon page (ASP) is in Application 1 the root. Since I test in Application 2 the ability to make a Session (cookie) and see if it exists in the logon page, the trouble appears.

 

[Aaron [SQL Server MVP]]

Yes, note that http://www.aspfaq.com/2157 also states that this can happen
across defined virtual directories...

--
http://www.aspfaq.com/
(Reverse address to reply.)




Thanks for cart.zip. I saw after this post this was the way to go. Trouble
is I am finding that different Applications are not not necessary for this
issue to happen. Consider this:

The root is a FrontPage 2000 Sever Extended web. Application 2 is also a
FrontPage 2000 Server Extended Virtual Directory of Application 1. In
Application 2 there is a ASP with this in it:

<img src="/images/spacer.gif">
<img src="/images/adobelogo.gif">

The first fails while the second one succeeds.

I haven't been able to track down that anomoly yet. Application 2 has an
images folder so I just stuck the spacer.gif in there and left the HTML
alone. That fixed it.

I know this isn't a Session issue but the ability to "share" across
Applications seems to be hazardous.

 

[Patrice]

Why do you use two applications ? I would just test this by using two pages
into the same application ???

Patrice

--

"George Hester" <[email protected]> a écrit dans le message de
Yes I was hoping that. This is just a way for determing if Cookies are
enabled. The accessed page (In Application 2) sends the client to a logon
page (in Application 1) if they don't have a Session not necessarily made in
Application 2. The logon page (ASP) is in Application 1 the root. Since I
test in Application 2 the ability to make a Session (cookie) and see if it
exists in the logon page, the trouble appears.