Thansk Luke. I'm not familiar with observers but will research them. Not yet knowing exactly what they are, I liked the fact that the after_save handler guarantees that all the after_save processing will be completed in the same thread as the save itself, thus avoiding the potential for any race conditions in a multi-threaded environment.
As for your second suggestion - if I understand it correctly, that is in fact what I am doing. The emission's after save handler calls emitter.update_emitter_emissions, which then runs through the entire list of emissions, making changes as necessary. But that doesn't eliminate the problem... Or did I misunderstand your suggestion here? On Mar 22, 8:53 am, Luke Pearce <[email protected]> wrote: > Could you use an Observer instead? Or perhaps do the reverse and have > the after_save of the emission call update_totals with its emitter? > > Cheers > Luke > -- > Posted viahttp://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
