tag:blogger.com,1999:blog-2813261110497121234.post7444119380546155322..comments2008-01-28T07:38:17.161-08:00Shane Harviehttp://www.blogger.com/profile/01016971334424471677noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-2813261110497121234.post-53750231497782744922008-01-28T07:38:17.161-08:002008-01-28T07:38:17.161-08:00Code sample I mean...CARFIELDhttp://www.blogger.com/profile/13094952618057460795noreply@blogger.comtag:blogger.com,1999:blog-2813261110497121234.post-17841115921371108672008-01-28T03:46:27.768-08:002008-01-28T03:46:27.768-08:00I've ended up building my own little callbacks for this kind of tasks. For example, I have users that can send messages to each other (as in IM messages, not Ruby method calls), so in my User R objects I now have macros like <I>before_send</I>, <I>before_receive</I>, <I>after_send</I> and <I>after_receive</I>, which get passed a reference to the message object. This way I can have different User subclasses react in different ways to different message types, etc., and the underlying message sending code remains untouched.<BR/><BR/>Basically, I try to not rely on AR too much when my domain is not really just about CRUD.ismaSanhttp://www.blogger.com/profile/12478978326569335706noreply@blogger.comtag:blogger.com,1999:blog-2813261110497121234.post-48640756568964522092008-01-28T00:42:43.596-08:002008-01-28T00:42:43.596-08:00If there is example then it would be great...Carfeld Yimhttp://www.blogger.com/profile/14027134382703629417noreply@blogger.com