I didn't get any response at all to this, though maybe a half a dozen people actually looked at the code. Being completely unfamaliar with the process of contributing code to the community, i'm not sure if this is what I should have expected or not.
Should i continue on with the idea of submitting this into CPAN or is the does the lack of reponse indicate that this is horribly useless and I should immediately delete it and pretend it never happened. Again, any (some?) feedback would be appreciated. Adam > -----Original Message----- > From: Adam Prime x443 > Sent: Sunday, November 12, 2006 12:09 AM > To: modperl@perl.apache.org > Subject: [RFC] Apache2::Filter::TagAware > > At ApacheCon this year Geoff gave a talk about Output filters > (slides: > http://www.modperlcookbook.org/~geoff/slides/ApacheCon/2006/mp > 2_filters-printable.pdf.gz) which included a sample handler > that ran the manual through HTML::Clean. a big part of the > code in the filter was to handle the possibility of having > split tags and that subsequently making HTML::Clean not play nice. > > Philippe gave a talk about Profiling and Instrumenting > (slides: > http://ectoplasm.org/Talks/mod_perl-2.0-profiling-9394.pdf) > in which a comment came up about using Filters to insert page > generation metrics into the body of the page the metrics were > about. This kind of filter too would have to handle the > split tags problem. > > So it occurred to me that this might well be handled by > subclassing Apache2::Filter and making the subclass handle > it. So after a bunch of screwing around I finally got a > pretty much working version. > > An example is running here: > > http://filtertest.kabob.ca/ > > It's running the manual through a filter that injects '!!' at > the end of each read call, basically just illustrating that > it's actually working. > > code here: > > http://kabob.ca/perl/Apache2-Filter-TagAware/lib/Apache2/Filte > r/TagAware.pm > > notes: > > What constitutes a 'tag' is user defined. it just takes a > regexp that defines an incomplete tag, the default being '(<[^>]*)$'. > > It only works with the stream filter API right now. I > haven't read any of the bucket brigade documentation, but I > assume that this idea could also be applied to that API as well. > > I'm not sure if i'm doing anything really weird or really > wrong here, so any and all comments are welcome. > > Adam >
