951791 - [clock] Remove singleton restriction on Timer

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::Clock, defect)

Description

[Mike Pennisi [:jugglinmike]]

Currently (due to the way it is persisted), the Timer class can only safely support one instance per context. This makes it effectively a singleton, although it is possible that future versions of Clock may call for multiple timers.

Re-structure the Timer code to support an arbitrary number of instances, and move  the assumptions about number of Timers to higher-level application logic (avoiding the use of global variables where possible).

Comment 1

[Marcus Cavanaugh [:mcav]]

(bug cleanup: if we support multiple timers in a future Clock version, we can modify the Timer class accordingly.)