On Fri, May 25, 2001 at 11:37:01AM -0700, Doug MacEachern wrote:
>
> i think we should focus on getting the rest of the direct C api
> mapping done, which we want in any case. with that in place, you
> should be able to prototype the approach you outlined here as a pure
> Perl module.
Yeah, I mentioned doing it as a subclass of Apache::Filter in that email
somewhere.
I think that two things are necessary to enable a pure Perl
implementation:
- adding is_BOS() and is_EOS() to Apache::Filter (or to
Apache::{Brigade,Bucket}, and
- allowing some kind of Perl scalar (including refs) to be passed in
to ap_add_xxx_filter() and then in to the handler sub.
Would exposing filter->eos be sufficient for Apache::Fitler->is_EOS()?
The is_BOS() would be nice for symmetry (lack of which is one of my
beefs about both bucket brigades and filter chains as they now exist in
apache).
Providing some Perl context structure passing mechanism is a must-have,
too, given that the same filter may be isntalled several times.
Providing this in the right way could also obviate the need for an XS
level is_BOS().
Allowing Apache::Filter instance subclassing would be really nice, but
just the above should be fine.
Do you want me to take a swipe at the above (don't want to duplicate
work you're planning on doing)?
- Barrie
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
