Bug 107594

Description Curtis d'Entremont 2005-08-22 09:29:14 EDT

We are using the Profiling Monitor to display and control our agents, however
these are not implemented using the agent controller. Rather than reimplementing
a new view to control these agents, we would like to use the same view as with
other agents. However, the problem is that the UI is too tightly coupled with
the agent controller.

For instance, our agents support start and stop monitoring, but the start/stop
actions in the profiling monitor are hardcoded to talk directly to the agent
controller, so they don't work for us.

The UI should be de-coupled from the back end as much as possible, such that you
can replace the backend and plug in a new one. The only way I can make this work
as-is is to try and short circuit the actions and add a layer of indirection so
that they don't talk to the agent controller for our agents. However, this is
only a temporary hack.. we need a real solution.

There should be a way to provide an implementation for each action, for each
agent. Thus, if I add a new agent to the UI, I should also provide an
implementation for the actions. I imagine something very similar to the eclipse
debug framework, where you plug in processes.