Hi, On Fri, Apr 15, 2011 at 2:06 PM, Rupert Westenthaler <[email protected]> wrote: > ...In summary > (a) only ensures that no remote services are called in OfflineMode it > does not communicate to the JobManager that an Engine can no longer be > used...
I agree with Olivier that that's good enough for now. It would be good though for canEnhance(...) to be consistent and return false when offline and computeEnhancements will do nothing. > (b) would only deactivate the engine, but also not tell why this > engine is no longer available > > so maybe we need a (c) where an engine can communicate some status > messages to the JobManager and extend the user interface.... Maybe later...the simplest might be be an additional return value for canEnhance(...): the reason why that method returns no, "system is offline" in this case, or a specific return value. -Bertrand
