Update...
How do you spell idiot? E-R-I-C-H
The refresh oddity isn't an embperl problem but the nut behind my
keyboard
The reason why the refresh wasn't behaving properly was a logic error...
I was populating the hash prior to doing the data updates. Hence, the
hash was always one record b
>
> One oddity I noticed yesterday... If I fill out the form and click "Add
> Another" this new entry isn't immediately shown. If I then fill out the
> form and click "Add Another" the previous record is shown. This is
> consistent. It seems that it's always one relative behind.
>
It's very h
Well the timestamps are different. Here's the head portion of the
logfile:
Logfile = /tmp/embperl.log, Position = 4150760, Pid = 3714
[3714]REQ: Embperl 1.2.1 starting... Fri May 26 08:55:49 2000
[3714]REQ: No Safe Eval All Opcode allowed mode = mod_perl (3)
[3714]REQ: Package = HTML::Embperl::
>
> Hmm... I changed my httpd.conf so embperl has virtlog set and the
> dbgLogLink option enabled.
>
> I run this page and, if I'm reading the output correctly, it appears
> that it is indeed getting this from cache. Evals: 661 Cache: 661 (100%)
>
No, this only means that the precompiled Perl c
Hmm... I changed my httpd.conf so embperl has virtlog set and the
dbgLogLink option enabled.
I run this page and, if I'm reading the output correctly, it appears
that it is indeed getting this from cache. Evals: 661 Cache: 661 (100%)
Is there anyway to tell embperl to disable caching on a page
>
> The very odd thing is it appears that scalar(keys %HASH) remains the
> same and won't update unless I click on a link or hit refresh (even if I
> do an 'undef %HASH' prior to loading it with data)...
Maybe the page isn't executed, but served from some cache. You may check
your embperl.log fil
