I've applied some fixes for mod_perl to build on aix.
I could only test with aix 5.1 on powerpc. Please test that things work on
other configurations.
__
Stas BekmanJAm_pH --> Just Another mod_perl Hacker
http://staso
The
difference between mod_cgi and mod_perl is that mod_cgi does not
activate the filter brigade until it has read all the headers.
But in the case of mod_perl, this "event" is valid only for handlers
which print their own headers, rather than using mod_perl API to set
them. In the generic cas
Stas Bekman wrote:
Since the mod_perl's internal STDOUT buffer isn't mangled if you re-tie
it later, and it'll be always flushed at the end of the request, there
is no *need* to flush on CLOSE. However in order to be consistent with
perl fh close behavior, it probably needs to be changed to flu
Jie Gao wrote:
Hi All,
I am getting the following error mesg:
Can't locate object method "run_access_checker" via package "Apache::RequestRec" at /usr/local/perl-5.8.0_threaded/lib/site_perl/5.8.0/xxx/.pm
for the section:
sub handler {
my Apache::Connection $c = shift;
my APR::Socke
Hi All,
I am getting the following error mesg:
Can't locate object method "run_access_checker" via package "Apache::RequestRec" at
/usr/local/perl-5.8.0_threaded/lib/site_perl/5.8.0/xxx/.pm
for the section:
sub handler {
my Apache::Connection $c = shift;
my APR::Socket $socket = $c
Mark James wrote:
Stas Bekman wrote:
Mark James wrote:
STDOUT is flushed prior to a fork to exec an external binary (rcs).
I understand the cause. But I hope that you agree with me that this is
an application's problem. If you haven't sent anything to STDOUT yet,
don't flush. And if this is n
Does anyone use this handler to make on-the-fly thumbs? I've used the
standard example code in my apache (1.3.27 with MP1) and it seems to
ignore the handler.
Any suggestions?
--
Steven A. Adams <[EMAIL PROTECTED]>
Stas Bekman wrote:
Mark James wrote:
STDOUT is flushed prior to a fork to exec an external binary (rcs).
I understand the cause. But I hope that you agree with me that this is
an application's problem. If you haven't sent anything to STDOUT yet,
don't flush. And if this is not under your control,
Chris Faust wrote:
Thanks for the fixes Stas,
I appear to be up and running now..
Just a FYI for reference, I updated the source via CVS and tried it again.
That time around I didn't get the TestConfig error but I got pretty much all
the same errors that I got on the first (non-cvs) build where i
The Bricolage team is pleased to announce the release of Bricolage-Devel
1.5.1, a beta release for what will soon become Bricolage 1.6.0. In
addition to all of the new features of the 1.5.0 release, this version
of
the open-source content management system fixes many bugs and adds many
new feature
The Bricolage team is pleased to announce the release of Bricolage-Devel
1.5.1, a beta release for what will soon become Bricolage 1.6.0. In
addition to all of the new features of the 1.5.0 release, this version
of
the open-source content management system fixes many bugs and adds many
new feature
Thanks for the fixes Stas,
I appear to be up and running now..
Just a FYI for reference, I updated the source via CVS and tried it again.
That time around I didn't get the TestConfig error but I got pretty much all
the same errors that I got on the first (non-cvs) build where it couldn't
find ini
12 matches
Mail list logo
