Comment 3 for bug 1217098
Revision history for this message
| Didier Roche-Tolomelli (didrocks) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
Hey Barry,
That doesn't sounds like a good way of designing the API. The UI shouldn't have to know if this errors is because the daemon timed out and wasn't able to restore its state or because something else on the system is screwed.
For instance, let's imagine we want to report automatically when ApplyUpdate() failed (in addition to the feedback from the user). So, we have to take into account the case "the daemon timeouts and this is excepted to fail" with "there is a real issue on the system"?