Stas Bekman <[EMAIL PROTECTED]> writes:
[...]
trying to understand what the problem is and how to write a test for it and how to fix it. will keep you posted.
The problem is that the current modperl_bucket.c implementation needs a proper setaside function. Think about it- the interpreter only hangs around for the request, but the bucket may be setaside in the core output filter for much longer than that.
There is no problem per se, since the setaside slot is marked as:
apr_bucket_setaside_notimpl, so noone can try to setaside it. However you are right that we may want to support that functionality, in which case your concern of perl interprter rightfully kicks in.
I tried to fix this by implementing a setaside function, but it was such a mess that I realized it would much simpler to just start over.
Th smoke tests pass for me now (no funky tainting going on now), but
I'm reluctant to post the patch until folks agree on how b0rked the
current implementation is.
As mentioned above, I don't think it's borked in it's current form. It's just incomplete. Though trying to complete it, may prove hard. On the other hand, it's very similar to pool cleanup handlers implementation, where we store my_perl along with data, and use it to work on the data later on. The concept should work just as well for the setaside function implementation. As I didn't try to implement that, please share the outcome of your attempts to improve it.
In any case I fail to see how the unsupported setaside functionality affects the problem in hand?
-- __________________________________________________________________ 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]
