In article <suppressed>, Flowers, Jay wrote: > So I have to manage several similar web sites. I came up with this to > reduce the time it takes me to write/configure them. > The modules I want to use I place in > @CGI::Application::FrameWork::Config::Modules array in the CGI scripts > BEGIN statement. At the beginning of the modules I register the > module's run modes. > > If CGI::Applications where written to be used in this manner many > written by different authors could be easily combine. Some manners that > would need to be laid out: > Modules of this type that are published can not use the start mode. > All run modes start with the name of your module. > > If these manners are adhered to then one could quickly piece together > several modules into one CGI App. > > What do you think? Hello Jay, Thanks for sharing this idea. From your example with the "Navigation" module, it looks like it provides some useful services that may be used by run modes, but are not run modes themselves. I am fond seperating "run mode" code from supporting services code, but this isn't a way that is intuitive for me to do it. Instead, I think about having modules that can be "used" and then provide extra CGI::App run modes that can be used. CGI::Application::ValidateRM works like this. Or alternatively, a module could have it's own OO interface, and the CGI::Application project would talk to it through that. That design seems the best to me, because it makes the module potentially available to non-CGI::App projects as well. In either design, it makes sense to me to "use" the supporting modules from the Run-mode modules that need them. What I think about the idea of having a instance script that patches together multiple run mode modules, I wonder why it wouldn't work to just have two instance scripts and create pages which hyperlink between them (assuming they really are seperate applications). Mark - http://mark.stosberg.com/ --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/suppressed/ To unsubscribe, e-mail: suppressed For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.