|
osdir.com mailing list archive |
|
Subject: A::Registry vs. mod_perl handler philosophy - msg#00561List: apache.mod-perlcurious as to how people decide between coding for Apache::Registry vs. mod_perl handlers. It's been suggested to me that content generating apps should be done under A::R, whereas logging, authentication Etc. should be implemented as mod_perl handlers. What is the opinion of the group? Regards, P -- ^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^ Peter Ensch, pensch@xxxxxx A-1140 (214) 480 2333 ^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^ Thread at a glance:
Previous Message by Date: click to view message previewRe: [ANNOUNCE] libapreq-1.2 releaseJoe Schaefer <joe+gmane@xxxxxxxxxxxxxx> writes: [...] > and at www.apache.org: > > file: http://www.apache.org/dist/httpd/libapreq-1.2.tar.gz > sig: http://www.apache.org/dist/httpd/libapreq-1.2.tar.gz.asc Correction- those urls for libapreq-1.2 should read http://www.apache.org/dist/httpd/libapreq/libapreq-1.2.tar.gz http://www.apache.org/dist/httpd/libapreq/libapreq-1.2.tar.gz.asc -- Joe Schaefer Next Message by Date: click to view message previewRe: A::Registry vs. mod_perl handler philosophyHi there, On Fri, 20 Jun 2003, Peter B. Ensch wrote: > I'm beginning to develop apps under mod_perl. I'm > curious as to how people decide between coding for > Apache::Registry vs. mod_perl handlers. Use Apache::Registry only if you have to in order to get legacy CGI scripts working. > It's been suggested to me that content generating > apps should be done under A::R, whereas logging, > authentication Etc. should be implemented as > mod_perl handlers. All new code should use handlers. 73, Ged. Previous Message by Thread: click to view message preview[ANNOUNCE] libapreq-1.2 releaselibapreq-1.2.tar.gz (Apache::Request) is now on CPAN: file: $CPAN/authors/id/J/JO/JOESUF/libapreq-1.2.tar.gz size: 277549 bytes md5: ae08726f11ca25a215d4d854d675c3ff and at www.apache.org: file: http://www.apache.org/dist/httpd/libapreq-1.2.tar.gz sig: http://www.apache.org/dist/httpd/libapreq-1.2.tar.gz.asc key: http://www.apache.org/dist/httpd/KEYS -------------------------------------------------- Changes since v1.1: =over 4 =item 1.2 - June 19, 2003 libapreq-1.2 released. =item 1.16 - June 19, 2003 Updated INSTALL & README documents to explain how to configure the tests. Apache::Test v1.03 is now a prerequisite for libapreq. =item 1.15 - June 13, 2003 Experimental support for SFIO is withdrawn. =item 1.14 - April 30, 2003 Add documentation for subclassing Apache::Request. [Steve Hay] =item 1.13 - April 18, 2003 Sync test suite uris with latest Apache::Test [Stas] Patch mfd parser's Content-Disposition header to do case-insensitive matches on "name" & "filename" keywords. This feature allows uploads from Nokia Series 60 phones to work as expected. [Oskari 'Okko' Ojala] Patch Request.xs to revert to using pre-1.1 $upload->fh code for pre-5.8 perls. This patch may get backed out prior to 1.2's release, unless it is known to resolve problems (zombies?) reported to occur with libapreq-1.1 uploads and pre-5.8 perls. [Joe] =item 1.12 - February 27, 2003 do a better mod_perl version checking, including the test for mod_perl 2.0. [Stas] Applied IKEBE Tomohiro's patch for handling %uXXXX strings. =item 1.11 - February 27, 2003 Add req->nargs to C API to distinguish between query string and request body params. Next Message by Thread: click to view message previewRe: A::Registry vs. mod_perl handler philosophyHi there, On Fri, 20 Jun 2003, Peter B. Ensch wrote: > I'm beginning to develop apps under mod_perl. I'm > curious as to how people decide between coding for > Apache::Registry vs. mod_perl handlers. Use Apache::Registry only if you have to in order to get legacy CGI scripts working. > It's been suggested to me that content generating > apps should be done under A::R, whereas logging, > authentication Etc. should be implemented as > mod_perl handlers. All new code should use handlers. 73, Ged. Loading Comments...
|
|
