Glenn Strauss wrote: [...]
What is/are the problem(s) we're trying to solve here? We can use "mod_userdir_user" to detect that it is a userdir request and that document_root does not apply, even if we can't get the userdir root path. We can't easily do the same for other mappings.
Well, actually, the question has nothing to do with userdir. I just thought (w/o looking at it) that it had some magical way to change ap_document_root that we didn't know about. But as you said, it doesn't.
The problem we are trying to solve is how to allow users to change the document_root value in the server config structure, w/o affecting other threads if run in the threaded enviroment.
We already agreed that it should be OK to change document_root in the non-threaded enviroment, where users will be responsible at restoring the value at the end of the request, should they wish to modify it. it worked perfectly fine in mod_perl 1, but it wasn't threaded.
With regards to mod_userdir, I had a thought about patching it to also provide "mod_userdir_group" and "mod_userdir_path" notes. Does that sound like a useful thing? Or, instead of in r->notes, this sort of userdir information seems useful for a new sub-struct in the request_rec. Wish me luck suggesting that on [EMAIL PROTECTED] :)
You will need more than just good luck. You should try to wait for the next big meteorite rain and who knows that may just work.
-- __________________________________________________________________ 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
-- 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
