(Originally posted in prototype users group) In regards to not being able to stop a timedobserver (see this thread: http://groups.google.com/group/rubyonrails-spinoffs/browse_thread/thr...), 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 "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~----------~----~----~----~------~----~------~--~---
