On, or in the near vicinity of Tue, 1 Jul 2003 11:23:00 +0200 Enrico Sorcinelli <[EMAIL PROTECTED]> has thus spoken:
On Mon, 30 Jun 2003 12:57:00 -0700 Adi Fairbank <[EMAIL PROTECTED]> wrote:
Apache::WebMessaging
I am about ready to release an intraserver web-messaging application for mod_perl. A brief description of the app follows; I'd like to hear some comments from the mod_perl/Perl/P5EE community on:
You could look about Apache::* modules naming conventions:
http://perl.apache.org/products/apache-modules.html#Module_Naming_Conventions
Apache::App::WebMessaging namespace could be a right place :-)
According to the asterisk note below Apache::App:: "However, if you are planning a substantial framework with many inter-related modules, you should probably go with a top-level namespace outside of Apache::."
This app already has 7-8 inter-related modules, though I would not call it a substantial framework. In fact it requires you to already have your own application framework setup in order to use it. It's basically a plug-in application for your existing mod_perl framework.
I could rename it to just WebMessaging:: but it is specifically designed for mod_perl, which is why I think it should go in Apache::.
Also, I noticed there are currently no Apache::App:: modules. Should this be the first??
Probably the best bet is to give it some cool unique name, like Apache::AdiChat and then you are all set, since you are not going to take over any future framework/namespaces...
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
