> The thing is I am getting some weird behaviour where one application seems
> to be getting code from the other. In theory this isn't possible with the
> separated namespaces. I suspect my UNIERVSAL use is the problem. Can anyone
> verify this? Is it a known problem? Is there any way around it?
To my knowledge, the only namespace which is separated is package main.
I don't know about you guys, but I think it would be great if mod_perl
could be as painless as mod_php. Don't get me wrong, I think that PHP as
a language is absolutely fubar, however mod_php is fast, secure, isp
friendly and does not have so many problems as mod_perl.
A list of things I've noticed:
* If you have two *different* modules which have the same name, then
either one, or the other is loaded in memory, never both. This is
dead annoying. I think Perl standard modules + CPAN modules should be
shared, other modules which are specific to a given script should not.
* Global variables should be reinitialized on each request. Or at least
if we want them to be persistent we do not want them to be shared with
different scripts on different virtual hosts!
* Perl garbage collector should be smarter (okay, that may not be a
mod_perl issue). C geeks out there, ain't it possible to compile a
version of Perl with a better GC?
* Despite numerous heroic efforts, HTTP HEAD requests are still screwed!
Apache::Registry serves HEAD + Body, and Geoffrey's Apache::HEADRegistry
doesn't work with redirects and 404's (I get like two headers and 3
bodies for 404's. Now that's verbose :-))
These are the - painful - issues I discovered during the last 6 month of
intensive mod_perl coding. I hope they'll be fixed at some point because
mod_perl could be so popular if they were!
Allright I'll stop whining and go back to some coding ;-)
Cheers,
--
IT'S TIME FOR A DIFFERENT KIND OF WEB
================================================================
Jean-Michel Hiver - Software Director
[EMAIL PROTECTED]
+44 (0)114 221 4968
================================================================
VISIT HTTP://WWW.MKDOC.COM
