> A radical thought: Given support for A::R in a
> new module from which C::A may inherit, is the
> "CGI" in CGI::Pipeline really appropriate? How
> about WWW::Pipeline, or even WWW::Application?
> Other thoughts? Or do we agree with the author of
> CGI::Application::Plus that "Namespaces are just
> words and does not means so much"? ;^)
Interesting point. With everything being plugged-in as a service, is the
application really web-specific at the core? Perhaps
"App::Pipeline", or if it could be used reasonable well
for handling a command line script as well.
Mark
--
. . . . . . . . . . . . . . . . . . . . . . . . . . .
Mark Stosberg Principal Developer
mark-WmyhgDpj2fCHT8/ATrE1yw@xxxxxxxxxxxxxxxx Summersault, LLC
765-939-9301 ext 202 database driven websites
. . . . . http://www.summersault.com/ . . . . . . . .
---------------------------------------------------------------------
Web Archive:
http://www.mail-archive.com/cgiapp-svx1JCNWaqPWzzAP45jFb16hYfS7NtTn@xxxxxxxxxxxxxxxx/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail:
cgiapp-unsubscribe-svx1JCNWaqPWzzAP45jFb16hYfS7NtTn@xxxxxxxxxxxxxxxx
For additional commands, e-mail:
cgiapp-help-svx1JCNWaqPWzzAP45jFb16hYfS7NtTn@xxxxxxxxxxxxxxxx
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
|