Should persistence be handled in the Result object?

[fmizzell]

In the FileFetcher we are not able to report progress because state storage is handled by the Job (The file fetcher), but the actual work is being done by other objects which have access to the Result object, but not the Job itself.

I still believe it is important for the job to have control over what and when things persist, but we need to somehow allow other processes objects to have a say also.

Maybe an event driven approach will work, in which the result object fire events that others can respond to?