At 06:04 PM 2/18/02, [EMAIL PROTECTED] wrote:
>I would catch user sessions in PerlInitHandler/PerlTransHandler,
>store/check them in PerlAuthzHandler, where I would also set the
>cookie, and close or refresh them in PerlCleanupHandler.
We do something similar, but we've segmented the process a li
On Thu, Feb 21, 2002 at 01:17:02AM +0200, Issac Goldstand wrote:
> [EMAIL PROTECTED] wrote:
> [snip]
>
> >As I need information between the stage of life, I would use $r->notes to
> >communicate down the cycle. But then again, if I have some data tied
> >to the session (I use Apache::Session), ho
[EMAIL PROTECTED] wrote:
[snip]
>As I need information between the stage of life, I would use $r->notes to
>communicate down the cycle. But then again, if I have some data tied
>to the session (I use Apache::Session), how can I give it to
>the PerlHandler. Is $r->notes proofed for any export, obj
Yep! Thanks for the book, it just arrived Friday. So now I'm sitting
on something what I wanted to do since a long time:
Splitting all my logic in the PerlHandler into PerlInitHandler, PerlTransHandler,
PerlAuthzHandler, PerlHandler and PerlCleanupHandler.
I would catch user sessions in PerlInit