On Tue, Feb 24, 2004 at 02:29:16PM -0500, Geoffrey Young wrote: > > > You probably want to talk to Geoff, since he said he has already started > > working on it. May be he has enough dough, so that you can finish it > > off. And as he said it'll will in the APR:: namespace, so there is no > > collision. I suppose once the core supports it, you can just nuke it > > from CPAN if you are happy with it. > > mock is much farther along with it than I am - I was creating it as a > tutorial for people who get a $bb and don't know what to do with it (as with > Apache::Upload). but they look surprisingly similar :) > > the one thing I was focusing on before I got sidetracked was support for $/ > - specifically if $/ is undef letting READLINE use $bb->flatten to return > the entire brigade, but also splitting the
This is a good idea... I'll see what I can do with my bits. > > another thing I was debating was how to treat the brigade when reading - you > seem to be treating the brigade like you would for Apache filters, > destroying the brigade while reading. I wanted more of a filehandle > interface where the brigade could be manipulated over and over again > (reading a file is non-destructive, as is APR::Brigade::flatten. > I think I need to read the Brigade docs again :). But, yeah, when I was building the thing, I was kinda thinking about it like it was a filter. Your approach sounds like it might be better though. > anyway, the (very, very rough) work in progress is here > > http://www.modperlcookbook.org/~geoff/modules/experimental/APR-TieBrigade-0.01.tar.gz > > debug statements and other ugliness included. but it might trigger some > ideas you had, or give you an idea as to how better use Apache-Test. for > what it's worth :) > Cool, I'll take a look and see what can be done. > anyway, I asked [EMAIL PROTECTED] to add an APR:: namespace to CPAN a while > ago, but they might not have gotten around it it yet. however, before > releasing to that namespace I'd consider a name that more specifically suits > the intended purpose - if indeed the module is only relevant to brigades use > in input/output filters, where you need to destroy the incoming and write to > a new outgoing, then I'd probably either keep it in the Apache:: namespace > to name it something like APR::TieFilterBrigade. also note that there > should be _zero_ mod_perl dependencies if placed in the APR:: namespace (I > wasn't quite there either :) I'll try and fix it up so it isn't destructive (if I can, and still make it work the way I need it to). I'm not sure if I can pull out all the mod_perl dependencies though. If that is the case it should stay in the Apache namespace, right? thanks mock -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
