Don't know if this will help or not, but maybe you'll get something
out of it to help your situation...
I had a similar problem. I didn't so much care to maintain the
session, but rather I wanted to have a seamless login from one
application to another and pass certain info. Couldn't get the
session to pass from one app to the next. You already mentioned that
you used a SQL DB to pass the info, and that is how I solved my issue.
It safe and secure.
A user logs into Application #1, I create an object that can hold any
relevant info (session info or Business info). When the user clicks
on a link to jump to Application #2: the first step I do is clear the
DB table of old info (if any exists), next I populate the DB table
with any relevant info I wish to pass (user info, session info,
business info, whatever...), next I redirect to Application #2 with a
URL variable that acts as a "flag" for the Page Load event in App 2 to
catch. This block of code in the Page Load event (if
url.flag_variable exists then...) calls the DB and populates an object
within App #2. Now anything I had in App #1 that I wanted to use in
App #2 exists as part of #2. The last step after populating the
object is to delete the record from the DB table.
You can use this logic to jump back and forth from one app to another.
Nothing needs to be passed in the URL, other than some dummy variable
that triggers a block of code to read the DB and populate an object.
Because you always delete at the end of this operation, there is never
sensitive info remaining in the DB. Obviously, depending on your
program's structure you would want to "tweak" this to suit your
program's needs. Good Luck.
"Brent" <b@b.com> wrote in message
news:10*************@corp.supernews.com... Umm, I'll try to explain better. I need the second app to completely run
on the other server, because it is a mapping program that people will choose
locations on a map. I then need to pass the value of that location back to
my app without it losing it's session.
