The ActivityMonitor framework (formerly named ProgressMonitor) is pretty complicated and difficult to use (or at least requires too much code to use properly). Plus, it doesn't really have the ability to capture a contextual history of activities/tasks. The amount of work and % complete really seems useful only for a UI and asynchronous monitoring capability, so that seem inappropriate here.

This framework should be simplified to support the main use cases, especially as its supposed to be used for allowing connectors to know the requests have been canceled (see DNA-217). These include:

• ability to determine if a task has been cancelled
• ability to record the duration and completion status of tasks and subtasks
• ability to record problems the occurred during tasks