Andrew McClain
2007-Apr-26 18:34 UTC
Why isn''t TimedObserver a subclass of PeriodicUpdater?
In regards to not being able to stop a timedobserver (see this thread: http://groups.google.com/group/rubyonrails-spinoffs/browse_thread/thread/6067fe242e4162a/11a81e092426b2f4?lnk=gst&q=observer&rnum=8#11a81e092426b2f4), I''m struck by the fact that Abstract.TimedObserver shares much of the same code as PeriodicUpdater. If we make TimedObserver a subclass of PeriodicUpdater, we reduce the codebase and get important methods such as stop(). Is there a compelling reason not to do this? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---