Yeah, admittedly, the support for custom job classes is clunky at best. I didn’t want to support it at all, but kept getting pull requests. Tried to explain it in the README, but it’s not easily discoverable. Generally, I stay away from plugins that change the job interface (ie: resque-status).

I’ll take a look at the pull request, but it sort of feels awkward to set a var to indicate custom job. That discussion can take place on github.

cheers,

ben

May 30, 2012 at 5:06 pm

Matthew Kocher says:

Thanks Ben – I think the confusions results from the naming of custom_job_class. It seems like it’s noise in the example, because your job name isn’t the name of the class. In reality, it’s what triggers calling the correct method.