Allows users in permitted roles to add custom help messages to any specific path or path pattern, for display to selected roles, along with help messages provided by other modules.
The DataSync module was written to schedule and execute jobs and import data in a much more scalable and reliable way than with cron.php and hook_cron. It allows you to schedule and run module-definable types of jobs on multiple servers in a centralized way. It uses database transactions in order to ensure that no data is corrupted while running multiple jobs at the same time. DataSync keeps track of the status of jobs and what phase they are in, so that if a job fails it can intelligently decide how to proceed. Almost all of DataSync's default behavior is overridable when you create your own job types.
DataSync has run over 180,000 jobs on our production servers already.
Warning: A bug introduced in CTools 1.2 causes the DataSync scheduler ajax forms to break. Either update your CTools to the 6.x-1.3 release or apply this patch.
Some of what DataSync for Drupal 6 does:
Runs scheduled jobs at any interval or as fast as possible
Provides an interface for you to schedule and timeout jobs on certain intervals
Provides an API for you to define those jobs
Handles job errors and timeouts gracefully
Allows you to run many jobs in parallel using database transactions
A Notifications plugin that allows users to subscribe to information updates based on a node's taxonomy. Primarily designed to integrate with nodeprofile to allow people to tag themselves, and receive updates based on the terms they have assigned to their nodes.
Usage examples
This module has been developed for School of Everything to keep users up to date on their interests. We use this module in conjunction with the taxman to allow users to tell us what subjects they are interested in.
This module also interfaces with Taxonomy NCO to provide notifications of similar subjects. Taxonomy NCO performs analysis on large freetagging vocabularies to infer semantic similarities, or 'other things that people might be interested in'.
A high level description of how this module was initially developed and implemented is available at http://drupal.org/node/284675.