[AURORA-181] make TaskObserver deal in objects

• Type: Task
• Status: Resolved
• Priority: Minor
• Resolution: Won't Fix
• Component/s: Thermos
• Assignee: Unassigned
• Reporter: Jonathan Boulle
• Created: 04/Feb/14 00:30
• Updated: 28/Dec/15 02:48
• Resolved: 28/Dec/15 02:48

Description

Per the long-lived comment on the TaskObserver class in apache/thermos/observer/observer.py ; now that there are new first-class objects for representing observed tasks (ActiveObservedTask, FinishedObservedTask), the TaskObserver should just return them for all queries, instead of generating janky dictionaries (which the HTTP observer often ends up doing further mangling of anyway).

This would
a) lead to a much cleaner interface between the TaskObserver and the BottleObserver (currently the only real interface to the observer)
b) make the TaskObserver much more usable as an API or even for command line use
c) make it much easier to develop other interfaces to the observer, e.g. a pure JSON-over-HTTP service