Robert Walker wrote in post #1034162: > The reason this happens is because Rails does not provide inter-model > change notification. Take the line:
Oh and BTW. If anyone is wondering why not just add a change notification system to ActiveRecord?Well, How far do you want to take that. It might be relatively straightforward if you have only a single instance of an application. However, to support scaling to multiple instances, maybe on several servers, you'd have to provide some sort of distributed change notification. Obviously, this complicates matters extensively. It's very much easier to just go back to the database to discover changes in the underlying state. -- Posted via http://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.
