On Tue, Feb 24, 2004 at 09:35:57AM -0800, Stas Bekman wrote: > You probably want to talk to Geoff, since he said he has already started > working on it. May be he has enough dough, so that you can finish it off. > And as he said it'll will in the APR:: namespace, so there is no collision. > I suppose once the core supports it, you can just nuke it from CPAN if you > are happy with it.
This works for me. > >stupid when I try to attach something like Mail::Audit to it. > >Apache::Net::Server::Mail::SMTP::Mail::Audit::PGP or something of the like > >is > >just aesthetically sucky. So, suggestions please? > > That's exactly where the problem is with your name choice. If you plan to > add things which are aren't Net::SMTP, then the name is wrong. As I > suggested it looks more like an application than a framework or protocol > API. It just happens to work only Apache. Therefore Apache::SMTP is > inappropriate. Usually when you write an application you give it some name, > not after the protocol but something else, usually unique and cool of > possible. e.g. Apache::MockMail. And several people have suggested to put > new Apache App modules into the Apache::App:: namespace, but it's up to you > to decide. You raise a good point. The App space seems like it would be more appropriate. MockMail, seems a bit pretensious ;), however I think your correct, SMTP is perhaps not right. How about Apache::App::SMTP? Can everyone else live with that? Alternatively, Apache::App::SMTPd. > > Meanwhile, I've linked to your module from: > http://perl.apache.org/docs/2.0/user/handlers/protocols.html#CPAN_Modules > as the first mp2 protocol implementation on CPAN, that I know of. cool mock -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
