Thanks ayhan for the detailed report, but had you used the latest cvs version,
it would have been much shorter ;)
I have been working on an output filter, using the bucket brigade API --
since the stream API still seems to have a flew kludges left to hammer
out.
You have to be more explicit of what kludges you are talking about. But first
get the latest cvs of mod_perl.
What I first thought would be a simple task has turned out to be quite a
deal though...
Here is some feedback that could perhaps be useful :
BRIEFLY (details are below)
-------
1) mod-perl (or perl-script) RESPONSE HANDLERS don't seem to send an EOS
at the end of the reponse.
This seems to be a major issue. ==> WORKAROUND : afaik, NONE
that is clean enough
You have to use the cvs version of mod_perl, where this has been fixed.
-------
2) Currently, there is no way to MIX & MATCH mod-perl FILTERS declared
via "PerlOutputFilterHandler" with APACHE standard ones.
==> WORKAROUND : It's so hairy & awful, I won't tell :-)
Need a way to "declare" (register) a filter in "httpd.conf" and later
activate it for a given context via the usual Apache directives (i.e
AddOutputFilter, AddOutputFilterByType, SetOutputFilter, ...)
IMHO, among all other options that are taken up in "todo/filters.txt",
this is the most versatile approach.
Yes, that's quite possible. Need to look at this issue.
*** 3) ----------- Subroutine attributes ------------------------
The SUBROUTINE ATTRIBUTES don't seem to work with Perl 5.8 (I recall
that they did work for Perl 5.6.1 though). Maybe I am doing something
wrong here but, the following code won't even compile :
# Code won't
compile under 5.8 !!!
use base qw(Apache::Filter); # Neither with this
#use Apache::Filter (); # Nor with this!
sub handler : FilterRequestHandler { # As long there is
"FilterRequestHandler" here.
...
...
}
Perl complains that it doesn't recognize the "FilterRequestHandler"
attribute. When Perl recognizes the attribute (such as for "locked",
"method", "lvalue"), it has no problems with it.
Did the Perl guys discourage the experimental attribute feature in 5.8
or something?
In my particular case, I was able to just leave out the attribute
altogether as it is the default (FilterRequestHandler). But if I were
writing a connection filer, I couldn't have...
Don't have this problem here, please try with the latest cvs again.
*** 4) ------------- Keeping filter CONTEXT : is it an issue ?
--------------------------
Keeping context between multiple calls to the filter has been an issue.
For this, I hear there will be a "$filter->ctx".
But then, is it really needed? The usual $r->pnotes() seems to be
working just fine for me.
Or am I doing something wrong by using pnotes for things like :
- Detecting a first call into the filter handler for a given
request
- Keeping context that concerns that concerns that particular
request
it's already implemented. $filter->ctx is better because it's private to the
filter and destroyed as soon as the filter is finished.
----------------------------------
As a final note :
I am using mod_perl 1.99.05 and Apache 2.0.40, which are admitedly a bit
old. I have, on the other hand, gone thru the CHANGES documents for both
upto the latest releases (MP 1.99.08 & A2.0.44). And there doesn't seem
to be anything that relates to the problems mentioned above.
because you should have read the Changes file of the cvs version.
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
