Thank you Robert and Patrick for such thought provoking posts. Notice how both of you are saying similar things to what Ar first suggested?
> Ar called it a "before_save callback function." >> Robert suggested, "I suppose I could have done the update >> automatically on save depending on the state of the claim. >> But, I chose instead to allow the user to update at their >> own discretion." >>> Finally Patrick thought of the copy-on-write feature. This got me thinking about rsync, or git; even Apple's Time Machine. All of these programs store data in a "state" that allows you to view the changes over a period of time. What is this design pattern called? Has it been written about? The software we use to run the business where I am employed has something like this on the accounting side. The whole, "close out the month", feature. Humm... -- 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 -~----------~----~----~----~------~----~------~--~---
