Re: Re: Scheduling without cron or modules

As am I, I purposely left it out to keep the post more to the point.

I'm writing a pre-packaged community website engine that'd I'd like to eventually distribute. I'm aiming for a very easy to use system, and very easy to read code. It should be as easy to set up, and require as little technical know how, as GreyMatter, MoveableType, Blogger and ilk.

I figured to this end I should avoid -relying- on any non-core modules, or cron, which in my Host Hopping adventures hasn't seemed to be so universally available.

This engine of mine supports a variety of plugins, like a chatroom modifier that uses Chatbot::Eliza, and advanced users will probably prefer an option to tie the software into cron. I still want a substitute coded in by default.

I have cron, I use cron, cron is good. But I think a less efficient/accurate mimic in my software would encourage wider use. Don't hesitate to let me know if you have a better point.

Comment on Re: Re: Scheduling without cron or modules

Replies are listed 'Best First'.
Re: Re: Re: Scheduling without cron or modules by vroom (His Eminence) on Aug 10, 2003 at 03:05 UTC
Schedule::Cron works very nicely for these types of things. Even if you don't want to use it looking at the implementation might give you a good starting point.	[reply]
Re: Re: Re: Scheduling without cron or modules by The Mad Hatter (Priest) on Aug 10, 2003 at 04:51 UTC
If it is going to be pre-packaged anyway, use whatever modules you want (such as the excellant Schedule::Cron) and just be sure to include them in the package you distribute. That isn't hard at all (as long as they are pure Perl). Just update the versions in your package when you release updates to your core engine, and allow for advanced users to specify that the system installed versions of the required modules be used instead. Simple.	[reply]
Re: Re: Re: Scheduling without cron or modules by graff (Chancellor) on Aug 10, 2003 at 05:10 UTC
vroom makes a good point. If you're going to be packaging up your goodies for the less technically inclined, it shouldn't be all that hard to embed a good cron module into your package. The same goes for any module that isn't part of the perl core, but would save you development time and offer a well-tested solution for issues that might otherwise be tricky for you or even risky for users of your package. Of course, when the CPAN module you embed or adapt into your package undergoes an important fix, you'll need to update your package accordingly. This could also be a very good feature for customers who are not "CPAN-enabled" -- they need only rely on you to make sure that their installation takes care of all that bug-fix/web-security stuff, so long as they just keep up to date on this one complete package that they get from you.	[reply]


"be consistent"
	PerlMonks