consider the lc() filter, which modifies each character in the string, but doesn't grow/shrink the string. currently we do a lot of copying in this kind of a filter when in fact this could be implemented with no copying at all (assuming that the buckets are plain data). instead of removing the bucket, reading the data, changing it, creating a new bucket and linking it to the bucket brigade, we could simply pass a callback to the bucket which will modify the bucket's contents without doing any copying.
I believe that this kind of "optimization" can be applied to filters like the "reverse" filter as well, even though you do have to move characters in memory this should be more effective to apply the reversing algorithm directly rathen than copying the data, reversing it, and then copying it back. __________________________________________________________________ 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]
