The odd i saw is:
'Sometimes' the script#1 wrongly displays 99 when the form in
script#1 is submitted. But it should display a empty string. The error rate
is about 50%. So I guess it is a problem of race condition, something like
this (i guess): Before %udat is saved to
I did some further testing today. I first tried the CVS version of modperl of
last night, no difference. But when I tried it with perl5.005_62 it worked like
a charm. It still has me baffled though, I'm looking more closely at the
changes between perl 5.005_03 and perl5.005_62.
On Wed, 10 Nov
On Fri, 12 Nov 1999, Jim Winstead wrote:
On Nov 10, Mark Cogan wrote:
At 10:10 AM 11/10/99 -0800, Ian Mahuron wrote:
I may implement IF/LOOPS/etc.. but not until I see the need.
Those introduce more complex problems.
And they are, of course, inevitable with almost any templating
Hi,
Thanks to Embperl I almost done my web. But then I found serious abnormality
on session handling (%udat) when used with HTTP redirection (ie. $req_rec->status(REDIRECT)).
Sometimes %udat works OK, sometimes it still remains old data, especially
after redirection is processed by another
hi,
i just ran into a *possible* bug in Makefile.PL:
if one wants to seamlessly build apache, mod_perl and other modules
using apaci with Makefile.PL, there is no way to *activate* other
modules, because they only get *enabled*:
perl Makefile.PL USE_APACI=1
Hi,
I think I also need to detail more about the problem i met with %udat
using Apache::Session::File before jump to Apache::Session::DBI because
the latter might also expose the same 'unsync %udat' problem.
Let me use these script segments to describe the odd output i met using
%udat with
Not really, just create a file called makepl_args.mod_perl such as:
--cut here--
# for Apache 1.3.6 and mod_perl 1.19+
# PERL_POST_READ_REQUEST=1 PERL_TIE_TABLES=1 PERL_SSI=1
# PERL_STACKED_HANDLERS=1 USE_APACI=1
EVERYTHING=1 USE_DSO=1 USE_APACI=1
According to Rasmus Lerdorf:
Those introduce more complex problems.
And they are, of course, inevitable with almost any templating
system.
You know, PHP was once just a templating system.
[...]
Then I figured it would be a good idea to add stuff like
IF/LOOPS/etc so I could
According to Rasmus Lerdorf:
Those introduce more complex problems.
And they are, of course, inevitable with almost any templating
system.
You know, PHP was once just a templating system.
[...]
Then I figured it would be a good idea to add stuff like
IF/LOOPS/etc so I
"Trevor" == Trevor Phillips [EMAIL PROTECTED] writes:
Trevor Another alternative is to get the MD5 base64 key to the
Trevor URI. My query is, what is the chance of two URI's giving
Trevor the same MD5? Is there any risk in it, or is MD5 guranteed
Trevor to give unique ID's? (I
Being fairly new to mod_perl I'd like to ask for an opinion and advice on
feasibility of writing an AccessHandler to act as a "front-end" to an
(Authen|Authz)Handler.
Basically what I'd like to do is have the whole site covered by one
Location / passing all requests to the AccessHandler which
On Sun, 14 Nov 1999, Leslie Mikesell wrote:
I think a lot of unnecessary complexity comes from the fact that
most of the template systems (and apache modules in general) want
to output the html as a side effect instead of accumulating the
page in a buffer or just returning a string containg
12 matches
Mail list logo
