Since perl can output byte code, perhaps this could be a good method for combining the apps in the way you suggest? We could create a convention for directories (for xml, xslt templates, perl code) combine the code and gzip/tar all the files together. We'd then need to create an Apache module that knows what to do when it sees that file, and maybe some way to cache the results so it doesn't need to uncompress the file each time.
Peace, or Not? __John Michael A Nachbaur wrote: > My discussion probably has nothing to do with what everyone thinks P5EE > entails, but it is something that I see is very important. My main interest > in perl is in the area of web development and deployment. While I love the > flexibility mod_perl gives me, packaging and configuring a complex site is > tedious. Now imagine if we have failover and loadbalancing functionality in > P5EE, how much more complex will the configuration of each web/app server > be? > > I'd really like to see the support of ".war"-like bundles under > mod_perl/Apache. For those of you unfamiliar with Java app servers, a .war > file is like a .jar file, except for web applications. It bundles the > configuration, libraries needed, classes and HTTP resources for the site. > You deploy that application, or site, on a server by dropping the .war file > in a directory. > > Now, this probably is more of a mod_perl change than a P5EE change, but I > wanted to toss my USD$0.02 in here, since I know CIOs won't want to worry > about configuration differences between application servers. > > -man > Michael A Nachbaur
