On Fri, Aug 15, 2008 at 12:50 AM, Woody Peterson <[EMAIL PROTECTED]> wrote: > We used to use persistent jobs implemented ourselves for an older version of > backgroundrb (not sure what version, something from 2006), but they weren't > delayed and didn't require polling. Polling isn't really that big of a deal > as far as hits to the database go, but I see negatives of this system, and > can't think of the benefits. The downsides to delayed persistent jobs are > your background tasks don't execute immediately, and you have more hits to > your database (although small). Shopify released a plugin to do exactly > this, so it has to be useful for something, but when you have scheduling > software like bdrb that does stuff immediately and without polling (and you > can make it save results to the database if you want), what would be an > example of something that benefits from this model of delayed > database-backed jobs?
Something thats super critical, shouldn't be lost if backgroundrb server crashes or anything like that. Can be run manually if that kinda thing happens. _______________________________________________ Backgroundrb-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/backgroundrb-devel
