At 14:05 16.06.2002, Jonathan M. Hollin wrote: >However, the major problem, as I see it is, is simply that people already >KNOW modules by a specific name and changing them is probably going to lead >to confusion and possibly even some bitterness. If I'm setting up a new >server I'm going to be mighty pissed to have to unlearn what I know about >the mod_perl module namespace... > >If you think this can be overcome (symbolic links on CPAN anyone?), or if >you see major support for your proposal, then you also have my vote. I >think your idea is sound and logical. Nice one.
Yes, this is true. But I wasn't planning on making people change their current modules. That would clearly create confusion. This is a proposal for new modules which might come, especially for mod_perl 2.0 Which brings me onto another matter: I forgot some categories in my initial proposal. As for mod_perl 2.0 many new possibilities exist, I think we'd need something like: Apache::Filter:: for native filters (and maybe split into Output/Input too?) Apache::Protocol:: for protocol modules.. And probably some more I suppose. Anyway, as I said, this is indicative only. -- Per Einar Ellefsen [EMAIL PROTECTED]
