It's a PHP class that's included at the top of every page that needs
session/authentication. It's cookie based only, no option for URL
propagation.
PHPLib can do the same, as well as some other classes floating around.
Chris
On Thu, 8 Mar 2001, Bill Rausch wrote:
> Date: Thu, 8 Mar 2001 10:21:37 -0800
> To: [EMAIL PROTECTED]
> From: Bill Rausch <[EMAIL PROTECTED]>
> Subject: Re: Re: [PHP] are sessions single threaded?
>
> Thanks Chris.
>
> I've been looking at the PHP source code and have tentatively come to
> the
> same conclusion about the file locks.
>
> I'm going to play around with the no-cookies option and see where
> that
> takes me.
>
> Bill
>
> PS: The roll-your-own that you did. Did you modify the PHP program
> or
> just handle it in your web pages?
>
>
> At 10:01 AM -0800 3/8/01, Chris Carbaugh wrote:
> >By not using cookies, each browser window would have it's own
> session,
> >propagated through the URL. Which I don't think you would want
> users
> >with multi sessions in an intranet app.
> >
> >You didn't mention how you are storing your session data, but I'll
> >assume it's the defualt (files). I would further quess that the
> >hanging that you are seeing is do to a lock on the particular
> session
> >file.
> >
> >Any body know for sure?
> >
> >I'm currently working on are pretty complex intranet app that has
> >mulitple frames, each needing access to the session data independant
> of
> >the others. In my situation, PHP sessions just couldn't do what I
> >wanted. I ended up rolling my own session/authentication scheme
> backed
> >by a DB.
> >
> >Chris
> >
> >On Wed, 7 Mar 2001, Bill Rausch wrote:
> >> Date: Wed, 7 Mar 2001 15:00:41 -0800
> >> To: Ernest E Vogelsinger <[EMAIL PROTECTED]>
> >> From: Bill Rausch <[EMAIL PROTECTED]>
> >> Subject: Re: [PHP] are sessions single threaded?
> >>
> >> At 4:04 PM -0800 3/6/01, Ernest E Vogelsinger wrote:
> >> >At 00:56 07.03.2001, Bill Rausch said:
> >> >--------------------[snip]--------------------
> >> >>What I mean is, if a user is connected to a php page that uses
> >> sessions and
> >> >>that is involved in a time consuming operation (say 20 seconds
> or
> >> more)
> >> >>before returning an answer, and the user also opens a second
> window
> >> in the
> >> >>same browser to connect to another page in the same site that
> uses
> >> sessions
> >> >>the second window will hang till the first operation is
> complete.
> >> >>
> >> >>While testing, I was able to show that if I don't use sessions
> this
> >> doesn't
> >> >>happen.
> >> >>
> >> >>I need to use sessions and would like to allow users to have
> >> multiple
> >> >>windows connected to my site (it is an intranet application).
> >> >--------------------[snip]--------------------
> >> >
> >> >try not to use cookies - use session keys via URL/hidden form
> >> fields. This
> >> >way multiple browser connects can have multiple session keys, and
> >> you won't
> >> >"hang"
> >>
> >> Thanks for the answer. Help me to understand please. Is this a
> >> limitation
> >> of PHP somehow or is it a limitation of the browsers. Why does
> not
> >> using
> >> cookies make a difference? Where would I go to find more
> information
> >> on
> >> this issue?
> >>
> >> ---
> >> Bill Rausch, Software Development, Unix, Mac, Windows
> >> Numerical Applications, Inc. 509-943-0861 [EMAIL PROTECTED]
> >>
> >> --
> >> PHP General Mailing List (http://www.php.net/)
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >> To contact the list administrators, e-mail:
> >> [EMAIL PROTECTED]
> >>
>
> ---
> Bill Rausch, Software Development, Unix, Mac, Windows
> Numerical Applications, Inc. 509-943-0861 [EMAIL PROTECTED]
>
>
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
