Yes that's right
> But the main problem for Chris is that the data is being updated while > calculations are in progress. To avoid having stale objects, the > transactions can be used. > > Of course, merging is totally different thing and is way more complicated. > But as far as I understand Chris needs to ensure that there are no stale > objects in the middle of an action (not user's one but a system's). > > Also that MagLev is really cool! (http://www.vimeo.com/1147409) So the concept there is like having a singleton-like ActiveRecord model object that persists across processes and even when the underlying contents changes, 2 different processes still have the same AR values (all because of their MagLev cache). *video just froze for me 3/4 of the way in* but I must say that is very impressive. I'll also take on board that concept of UnitOfWork, and perhaps the way I think about this should be different Thanks guys for all your input and feedback, I really appreciate all of your comments and it's made me think differently this morning. Cheers -Chris -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" 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/rails-oceania?hl=en.
