Hi Indrek,
Thanks for the feedback.
At 03:51 PM 5/1/2000 -0500, indrek siitan wrote:
>gerald's logic (probably, I can't speak for him :) is that there
>should be no need for cookies - just use the %udat hash instead.
>this eliminates the need for session-cookies, but there might still
>be a need for saved (with Expire date) cookies in some situations.
I agree with your analysis. In my case, we have many scripts, not just
EmbPerl or even Perl at all. My company uses an architecture that
identifies customers based on cookies, and if EmbPerl couldn't work with
that at all, we couldn't use EmbPerl. Fortunately, CGI.pm allows me to
read cookies, and you point out another method below. But I can't see any
reason not to include better control over cookies in EmbPerl itself.
>at the moment, you can create the %cdat hash yourself with the
>following code:
>
> [-
> @ckpairs=split(/; /, $ENV{'HTTP_COOKIE'});
> foreach $pair (@ckpairs)
>
> ($name, $value) = split(/=/, $pair); $cdat{$name}=$value;
> }
> -]
Interesting, that gives me a useful piece of information too. Thanks!
> > This sounds like a caching bug.
>
>I don't know about this one, but Embperl has had numerous caching
>issues in the past. I searched my mails and found one quick patch
>that should fix at least some of the caching issues in the 1.2
>versions:
Thanks for the tip!
steve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
