On Fri, 15 Feb 2002, Gunther Birznieks wrote: > But in this case it would be a P5EE guide to CPAN. What > exists on CPAN (and elsewhere) written in Perl that can > be used to solve things that people might do in J2EE and > what are the pros and cons to these items.
in that vein, check out something i wrote up a while back: http://cvs.perl.org/cvsweb/p5ee/P5EEx/Black/docs/webapp-spec/requirements.txt?rev=1.1 the parts i'd like to highlight are the ones entitled "example of apache as both web server and container" and "example of apache as web server with external container (wombat)". my goal was to illustrate the differences in configuration between a typical conglomeration of cpan modules and wombat. it assumes the following environment: - all web uris with the .mhtml extension handled by mason - database connection pooling - authentication and authorization against a mysql database - session id tracked via cookies - session data cached in shared memory - application docroot in /www/myApp with urlbase /myApp - /myApp/login.mhtml presents a login form, including login error messages - webapp "tmpdir' (location varies) - log messages written to a local file (location varies) there's probably a lot more that could be added to this laundry list of "standard webapp components" and worked into the config examples (the hashed, encrypted, compressed, rolle up and smoked cookie values as per recent modperl list thread). this would have the auxiliary benefit of suggesting new features for wombat :) (hopefully this writeup illustrates one of my points about the irregularity of configuration styles across the set of apache modules. in the all-in-one apache example you've got: PerlModule, <Perl> sections, PerlSetVar, Perl*Handler. you're required as a deployer to know the names of class methods. in the wombat example, you have a simple high level configuration language, where the lowest level piece of code component information is the class name.) furthermore: i also started writing up a capabilities comparison between the apache api (including Apache::Request) and the servlet api: http://cvs.perl.org/cvsweb/p5ee/P5EEx/Black/docs/webapp-spec/capabilities.txt?rev=1.1 the goal was to highlight the differences between the two apis so that web application framework "vendors" (gerald, matt, jon/dave, gunther, etc) could see exactly what functionality could be gained with a common webapp api. i was hoping that once i completed the document, i could get everybody to rank their interest in each of the points so that we could come up with something that would be compelling enough for each product to support. > I have a small excuse. I program Java almost exclusively > these days. :) my excuse is short attention span. i wrote the documents referenced above late one evening several months ago. i haven't had the inclination to get back to it since. got my hands in too many pies i guess. i sure wish somebody out there with some fire in their gut would pick up where i left off tho.
