Again, please separate questions in separate threads. As these threads tend to grow big, it becomes really hard to manage them. Thanks.
> would it not be better to separate plain-old response > handlers from, say, filters.
What do you mean? Making it easy to derive from the handler's package whether it's a filter or not?
Sure, go ahead and call your filter modules Apache::FilterFoo or Apache::Filter::Foo. I'm going to release shortly Apache::Filter::HTTPHeadersFixup and probably Apache::Filter::Debug.
> Now that 1.99_10 is out, and that the filter API hasn't changed for a > whole 6 months :), I'd like to release on CPAN a general-purpose > output-filter as a replacement for "Sandwich", but which can also work > with wrapper templates (it's called CheeseBurger right-now). > > The code has been there for a while and works. I just need to add > support for the Sandwich options, so that it would be a drop-in > replacement. > > Under which namespace do I release it?
Either Apache::Sandwich, or if you want to stress that it's a filter Apache::FilterLayers or Apache::FilterSandwich, or you might want to poll the modperl list... Also it's probably a good idea to ask the owner of Apache::Sandwich whether they aren't working on a mp2 port already.
__________________________________________________________________ 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]
