Brett Sanger wrote: > > > Are any of you doing this? Do I have to turn each of this scripts into > > mini CGI::Applications? I suppose this wouldn't be a huge deal, but it > > would be nice to have another option. I'm not new to using, but > > relatively new to creating, OOP code. > > Can you make those methods into their own, independant modules, that both > yoru SuperClass and your cron scripts make use of?
This is the solution I use in similiar cases in Cascade ( http://www.summersault.com/software/cascade ). Functions that are shared between CGI::App and command line utilities are in their own modules that are not tied to CGI::App. I used this to create a script that import a Netscape bookmarks file into the content management system, and to facilitate a link validator that runs via cron. I've been very happy with that design. I had already made the distriction between "run mode modules" and "data munging" modules before I realized the need for these command line utilities, so my paradigm didn't have to shift very far to support it. :) -mark . . . . . . . . . . . . . . . . . . . . . . . . . . Mark Stosberg Principal Developer [EMAIL PROTECTED] Summersault, LLC 765-939-9301 ext 223 website development . . . . . http://www.summersault.com/ . . . . . . . --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
