Hi,
>
>
> >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.
>
You are wrong. There is no other reason for not supporting cookies directly
other then nobody has implemented it so far. If my logic were that %udat is
enought, then didn't had include questions about how to set a cookie in the
FAQ.
> 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.
>
I agree to you that there is no reason to not include it in Embperl, other
than the time it takes to do so. I put it on the TODO list (but there are
already I lot of things todo). Anyway you are free to send me a patch and I
will be happy to include it in Embperl.
>
> >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:
>
This is an very dangerous answer! There were a caching bug in earliy 1.2
beta version (I think < 1.2b4). Nobody really should complain about a bug in
a that is more than a year old! If you send a patch, please tell to which
version is applies, otherwise you can make things more bad.
Most of the things what you call "numerous caching issues" are because of
problems people have with the fact how Perl manages it's modules and
namespaces and not due to Embperl.
>Also, I have noticed that when I restart apache, usually EmbPerl will not
>run any scripts I have been working on; when I connect to the server, it
>sits there forever and the script never runs, or at least never returns a
>result to the browser. However, as soon as I make a change to the script
>and save, the script will run. This sounds like a caching bug. The
>obvious workaround is to re-save the file.
Steven, which version of Embperl you are using? There is no caching bug in
the current version of Embperl. There must be another reason for this strang
behaviour.
Looks like more to me, that your code needs a recompile before it could run
correctly after a restart.
Please try to put various
[- warn "text" ; -]
in your script, to see if it ever get called or where it stops working.
Is this first request a POST request? Does it involve CGI.pm?
Gerald
> Thanks for the tip!
>
>
> steve
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting
Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925151
WWW: http://www.ecos.de Fax: +49 6133 925152
-------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
