You cannot avoid using cookies. When you use Sessions web server is making
use of cookies (unless you go for URL rewriting) which remains in the
browser until one quits the browser.
To tackle your situation, you can effectively make use of a database table
and a session cookie:
1. set a sessi
Why not share a session DB across both servers?
Since your users disable cookies you'll have a url that looks
like this anyway: http://www.myPHPserver.com/index.php?sid=12345
if you wanted to maintain session state
so, when redirecting to the ASP server do:
header('location: http://www.myASPser
http://www.w3.org/TR/SOAP/
~ Matthew
-Original Message-
From: Mark McCulligh [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 21, 2002 4:14 PM
To: Jay Blanchard
Cc: [EMAIL PROTECTED]
Subject: Re: [PHP] Re: Passing variables between servers
I have thought about this also, but I need
y Blanchard" <[EMAIL PROTECTED]>
To: "'Mark McCulligh'" <[EMAIL PROTECTED]>; "'Seairth Jacobs'"
<[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, August 21, 2002 3:34 PM
Subject: RE: [PHP] Re: Passing variables between s
[snip]
The session variables are need on both server for authorization needs.
The two servers host two separate Intranet apps and I am trying to join the
two together into one Intranet app. The variable will be used on both
sides.
The reason I don't what to use cookie is your users keep disablin
The session variables are need on both server for authorization needs.
The two servers host two separate Intranet apps and I am trying to join the
two together into one Intranet app. The variable will be used on both
sides.
The reason I don't what to use cookie is your users keep disabling them.
Is there any reason to pass the data to the ASP server other than the need
for the ASP server to pass it back in case the PHP server session has
expired? If not, why not just store the login information in a local table
referencable by a primary key that you pass around instead? You could even
d
7 matches
Mail list logo
