pereinar 2002/10/01 07:58:06 Modified: src/products apache-modules.pod products.html Log: Added product: @Mail Submitted by: Ben Duncan <[EMAIL PROTECTED]> Revision Changes Path 1.2 +85 -18 modperl-docs/src/products/apache-modules.pod Index: apache-modules.pod =================================================================== RCS file: /home/cvs/modperl-docs/src/products/apache-modules.pod,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- apache-modules.pod 16 Jun 2002 12:04:17 -0000 1.1 +++ apache-modules.pod 1 Oct 2002 14:58:05 -0000 1.2 @@ -30,24 +30,6 @@ methods. -=head1 Playing Your Part - -Apache and Perl are world-wide collaborative efforts; naturally, the -Apache/Perl integration project is the same. You've started on the -right foot simply by reading this document, thanks! Please make sure -you've read the main Perl module list at -http://www.cpan.org/modules/00modlist.long.html, all that is said -there is relevant here! - -If you wish to share your module(s) in the Perl way, by putting them -on CPAN, send a request to modules@perl.org to get set up with a PAUSE -user id and directory. See http://www.cpan.org/modules/04pause.html -for more details. - -B<HINT>: For a nice set of template files try this: - - % h2xs -AX -n Apache::YourPackageName - =head1 The Module List Like other CPAN modules, the Apache/Perl modules are listed on the @@ -69,3 +51,88 @@ and C> book by Lincoln Stein and Doug MacEachern. If you can't find these modules on CPAN, look for them at http://modperl.com:9000/book/source/. + +=head1 Playing Your Part + +Apache and Perl are world-wide collaborative efforts; naturally, the +Apache/Perl integration project is the same. You've started on the +right foot simply by reading this document, thanks! Please make sure +you've read the main Perl module list at +http://www.cpan.org/modules/00modlist.long.html, all that is said +there is relevant here! + +If you wish to share your module(s) in the Perl way, by putting them +on CPAN, send a request to modules@perl.org to get set up with a PAUSE +user id and directory. See http://www.cpan.org/modules/04pause.html +for more details. + +B<HINT>: For a nice set of template files try this: + + % h2xs -AX -n Apache::YourPackageName + +=head2 Module Naming Conventions + +Like for normal Perl modules on CPAN, the C<Apache::> namespace +conventionally used for mod_perl modules needs to keep a certain +organization. This is why you should choose a multi-level name for +your module, categorizing it into a namespace that you feel fits your +module. There should be a very good reason for a module to not have a +nested name (ie. living directly under C<Apache::>), that should only +be the case for the core API modules and older modules which may keep +their names. + +Here are some examples of namespaces that you may want to use: + + Apache::App Applications: any module serving content with a + point-and-click interface * + + Apache::Auth Modules related to general user authentication/authorization + + Apache::Authen Modules solely related to authentication + + Apache::Authz Solely related to authorization + + Apache::Access Only access control + + Apache::Config Configuration-related things + + Apache::Devel Development-related modules (debug/devel help) + + Apache::Filter Filtering modules + ::Output Output filters (1.0 style Filter/OutputChain or 2.0 style) + ::Input Input filters + + Apache::Framework Modules providing application frameworks (templating + and/or publication frameworks) * + + Apache::Log Logging modules + + Apache::Method Method handlers (PATCH/PUT and the like) + + Apache::MIME MIME-type modules + + Apache::Monitor Monitoring modules + + Apache::Persistent Modules providing for persistency in connections + + Apache::Proxy Proxies + + Apache::RPC RPC/SOAP modules + + Apache::Trans URI Translation handlers + + Apache::Util General-utility modules, usually not handlers but + providing an API to use in your code + +C<*>: If you are writing a small application or templating module, +contained in one module, you can use these namespaces. However, if you +are planning a substantial framework with many inter-related modules, +you should probably go with a top-level namespace outside of +C<Apache::>. + +B<Note:> I<Of course> none of these categories are cast in stone: you +should feel free to choose the module name that suits your module best +instead of trying to follow these general indications. If in doubt, +just ask around at the mod_perl list; you are sure to get some +assistance in naming your module! Furthermore, you should look at the +way it's done on CPAN, and apply it under the C<Apache::> namespace. 1.14 +13 -0 modperl-docs/src/products/products.html Index: products.html =================================================================== RCS file: /home/cvs/modperl-docs/src/products/products.html,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- products.html 29 Jul 2002 07:56:54 -0000 1.13 +++ products.html 1 Oct 2002 14:58:05 -0000 1.14 @@ -177,6 +177,19 @@ written in Perl, has full support for MIME (and mod_perl) and is quite pretty. </li> +<li><p><a href="http://webbasedemail.com/";>@Mail</a> is a fully +featured Web Mail server that allows you to set up Web Mail at your +domain or server existing POP3 accounts. Including full source code, +under a commercial license.</p> + +<p>@Mail Includes auto-account creation via Sendmail/Exim/Qmail , +scheduler, SQL mailbox support, spell check, group address-book, user +preferences, multiple accounts, migration scripts from other +mail-servers, attractive DHTML interface, Anti-Virus integration, User +Payment service and in-depth Web-based administration of +accounts. </p> +</li> + <li> <a href="http://namp.sourceforge.net/";>Namp!</a> is Not Another Music Player. In combination with the Apache web server and mod_perl, Namp! lets you create a virtual jukebox of your MP3, WAV and Ogg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
