[cgiapp] Re: Idea for Super class of CGI::Application

[Mark Stosberg <suppressed>]

In article <suppressed>, Flowers, Jay wrote:
> 
> That is black box integration, I am proposing white box, or glass box
> integration.  Say I want to make a web page that uses two or more
> pre-packaged CGI::Apps, I need to users to authenticate to my site, as
> well as CGI::Carp carpout.  This would be a pain to maintain three or
> more scripts, don't more get I need to write a script to glue them
> together.  If they where written to use this super class then all I
> would need to do is create my glue module, probably just navigation, a
> super class of my own to provide authentication in the pre-run, and the
> script would handle the carpout.  This is much easier to maintain than
> three or more different scripts.

I see, this makes more sense to me now. What it sounds like to me is
that you are trying to control several otherwise stand-alone CGI::App
modules in a uniform way. You don't want to put "CGI::Carp" or
autentication in these modules, because they may used other ways. You
won't want do too much in the instance scripts because you don't want to
maintain several bits of syntax in several instance scripts. 

It's an interesting idea. I'm curious to know more about other people
think. The list seems a little quiet lately. No one was responded yet to
my post about a new module idea, either. :)

	Mark

--
http://mark.stosberg.com/ 


---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/suppressed/
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed