Since you are on the same server, I hope you mean the same domain.
If not the session variable wouldnt work very well.
But if you infact are on the same domain, you should look into the session
variable and store everything you need. From what I know there are now
limits on how much you can store
Dennis Gearon wrote:
What I'm trying to achieve is to have the same cookie IDENTIFY a user on
different (or same) applications (on the same server), but require them
to log in for each application, and get a different session.. Basically,
to keep separate 'user trails and in process variables'
With get varaibles, it's possible to always have get variables on a
page, even without a form, by simply appending the Get variables to the
end of the URL.
Is there anyway to do the same with Post variables? For instance, a
javascript that onUnload submit, or something?
--
PHP General Mailing
Dennis Gearon wrote:
With get varaibles, it's possible to always have get variables on a
page, even without a form, by simply appending the Get variables to
the end of the URL.
Is there anyway to do the same with Post variables? For instance, a
javascript that onUnload submit, or something?
Dennis Gearon wrote:
With get varaibles, it's possible to always have get variables on a
page, even without a form, by simply appending the Get variables to the
end of the URL.
Is there anyway to do the same with Post variables? For instance, a
javascript that onUnload submit, or something?
What I'm trying to achieve is to have the same cookie IDENTIFY a user on
different (or same) applications (on the same server), but require them
to log in for each application, and get a different session.. Basically,
to keep separate 'user trails and in process variables' for different
tabs
Dennis Gearon wrote:
What I'm trying to achieve is to have the same cookie IDENTIFY a user
on different (or same) applications (on the same server), but require
them to log in for each application, and get a different session..
Basically, to keep separate 'user trails and in process variables'
Dennis Gearon wrote:
What I'm trying to achieve is to have the same cookie IDENTIFY a user on
different (or same) applications (on the same server), but require them
to log in for each application, and get a different session.. Basically,
to keep separate 'user trails and in process variables'
What I'm trying to achieve is to have the same cookie IDENTIFY a user on
different (or same) applications (on the same server), but require them
to log in for each application, and get a different session.. Basically,
to keep separate 'user trails and in process variables' for different
tabs
Hi,
a cookie is path-specific - can that help you?
Frank
At 10:54 PM 8/23/2004, you wrote:
What I'm trying to achieve is to have the same cookie IDENTIFY a user on
different (or same) applications (on the same server), but require them to
log in for each application, and get a different
10 matches
Mail list logo
