Yes, I too have setup jserv and mod_perl under separate httpds and again,
XSL support, Oracle's XSQL thing, and the scalability of the servlet model
have all been compelling. But I do like being close to the Apache API,
for making Apache do really wacky things, mod_perl is unparalleled.
Besides, I've ported some mod_perl handlers to servlet API, it turns into
3 times the quantity of code. mod_perl let's simple things be expressed
simply and hard things possible :)
If anybody else is interested in implementing Cocoon in Perl, maybe we
should talk off line -- I'm too busy to write my own XSL transformer
library now in Perl (who has had time to follow the fluidity of XSL
anyway?? geez!) but I think it's sorely needed. There are three
or four different java XSL transformers that I know of; none in Perl!
BTW, using DSO's for development is fine but I would build static httpds
for production. For instance, I was just having some failures with
Apache::DBI under DSO that never hit me as static builds. So since I
build everything on my laptop DSO, I just had to forego persistent db
connections when I'm developing on it.
-Ian
Meanwhile, back at the ranch...
> Mostly I am investigating java because we have data
> that can be obtained in xml and formatted using
> various xsl stylesheets and there is no support
> for this in perl yet (and I'm too lazy to write my
> own). I am very impressed by the ability to develop
> the java servlets on windows or unix and copy the
> servlet bytecode to the other and run it unchanged.
> Likewise you can transparently run the apache on
> one machine and the jserve on another without regard
> to the operating system.
--
Salon Internet http://www.salon.com/
HTTP mechanic, Perl diver, Mebwaster, Some of the above
Ian Kallen <[EMAIL PROTECTED]> / AIM: iankallen / Fax: (561) 619-0995
