Hi,
All this talk of MVC and a universal despatch mechanism has
started me thinking about Java Web Applications and how they are bundled
into a standard configuration (e.g., Java's Servlet standard 2.3)
Would such a standard (albeit optional) be useful for mod_perl2?
Generally standards run contrary to the TMTOWTDI approach of Perl
but there are some advantages in a 'minimal' mod_perl web application
standard:
* ISP's could install mod_perl applications in a uniform/consistent way -
(e.g., the standard should prevent name space collisions etc.)
* A subset of mod_perl methods could be selected as a basis for the
standard allowing other 'container' servers besides Apache (e.g., like
http://jetty.mortbay.org - except in Perl not Java)
* Software companies (not sure who) could provide
replication/clustered/load balanced solutions based on this standard
* Application configuration/management tools could be used to administer
mod_perl application(s) on the same server(s)
* We could share 'mod_perl' applications on CPAN more easily/quickly
Ideally, I'd like to download a single mod_perl archive file
(e.g., application.mod) place it in a 'standard' application directory and
then point my browser to the new application.
Is this something that could be considered with the next release
of modperl2?
I'm thinking of something that is really 'lite', not too
prescriptive, but achieves the objectives above.
Nigel
> Ward Vuillemot wrote:
> > I know we are straying WOT, but I would love to get a better feel for XML, XSLT
>and AxKit.
>
> Barrie Slaymaker has written a couple of articles on perl.com that serve
> as a good intro to AxKit.
>
> - Perrin
>
--
Nigel Hamilton
Turbo10 Metasearch Engine
email: [EMAIL PROTECTED]
tel: +44 (0) 207 987 5460
fax: +44 (0) 207 987 5468
________________________________________________________________________________
http://turbo10.com Search Deeper. Browse Faster.
