News for hackers. Stuff that matters.
Re:Rails 4.2.0 beta1: Active Job, Deliver Later, Adequate Re... by hayksaakian on Wednesday August 20, 2014 @02:44AM (#8201327)
Beware, this behavior lets you shoot yourself in the foot because when you conduct your job, you might be working with a stale object that's changed since the job went on the queue.
Re:Rails 4.2.0 beta1: Active Job, Deliver Later, Adequate Re... by DouweM on Wednesday August 20, 2014 @04:46AM (#8201561)
That's incorrect. This is not YAML-style full object serialization, but rather a global ID being sent along the wire that is transparently looked up at deserialization.

See the example here: https://github.com/rails/rails/tree/master/activejob#globali...

Re:Rails 4.2.0 beta1: Active Job, Deliver Later, Adequate Re... by hayksaakian on Wednesday August 20, 2014 @05:31AM (#8201656)
Is it? I assumed it worked like delayed_job which gave me issues due to the problem I mentioned.
Re:Rails 4.2.0 beta1: Active Job, Deliver Later, Adequate Re... by DouweM on Wednesday August 20, 2014 @06:03AM (#8201727)
It is! That's the exact problem ActiveJob+GlobalID tries to solve.
Re:Rails 4.2.0 beta1: Active Job, Deliver Later, Adequate Re... by hayksaakian on Wednesday August 20, 2014 @01:23PM (#8203309)
I suppose I was mistaken then, thanks for helping me understand.
Re:Rails 4.2.0 beta1: Active Job, Deliver Later, Adequate Re... by volkk on Wednesday August 20, 2014 @10:20AM (#8202366)
why bother spreading false information without even taking a minute to read into what it actually does?