Emmanuel Gomez

I think you're absolutely right. I have Meta extending Timestamps right now to preserve the existing interface for as long as possible. Well, at least until I talked to you...

I went ahead and pulled out a JobIdentity plugin, which makes a total of 3 (JobIdentity, Meta, and Timestamps). I was wrong about moving Metadata in the class hierarchy, it...

A couple more fairly large changes, but I think quite simplifying: I moved #enqueue from Meta to JobIdentity and added before_enqueue hooks to facilitate creating the metadata before the job...

Oh, and I should mention that all tests are passing (after some updating) and that this might be three (small) resque plugins now. Also, I'm going to see if there's...

No dice on getting this merged in upstream. I opened an issue against Resque (defunkt/resque#244), but then I noticed that this was discussed long ago: defunkt/resque#6.

OK, there was some more opportunity for improving coherence by moving left-behind methods from Metadata into Timestamps::Metadata. This finishes the job of extracting Timestamps from Metadata. I also changed the...

The reason for putting the get/load/store methods in Metadata: _coherence_! Those methods deal with Metadata instances, and the alternative is to put the responsibility for get/load/store of Metadata instances on...

Hi @lmarlow! It's been a while since last I heard anything about this. Do you have any interest in merging in these improvements?

No problem, I just was looking through my repos and realized that I didn't know your thoughts about these changes. Let me know if there's anything you're concerned about once...

Still seems to be a problem: ``` CoreOS stable (962.0.0) Update Strategy: No Reboots core@localhost ~ $ systemctl status localhost State: running Jobs: 0 queued Failed: 0 units Since: Thu...