On 14 April 2012 20:25, Michael Hennebry <hennebry@xxxxxxxxxxxxxxxxxxxxx> wrote:
Waiting for a timeout implies a reasonably sane state of affairs regarding any data in transit, and if the worst has already happened then it's not going to make any difference. Either way, it forces the end user to make a hopefully sensible decision about how to reset the device and recover from the situation.
If, on the otherhand, you do a soft reset of the device and resume transfering data... Well, think about the garbage that can come out of a printer when jobs go wrong, now imagine that being written to a hard disk, tape drive, etc.
Under what circumstance would killing a waiting process
be worse than a process that should have waited,
but terminated instead?
Waiting for a timeout implies a reasonably sane state of affairs regarding any data in transit, and if the worst has already happened then it's not going to make any difference. Either way, it forces the end user to make a hopefully sensible decision about how to reset the device and recover from the situation.
If, on the otherhand, you do a soft reset of the device and resume transfering data... Well, think about the garbage that can come out of a printer when jobs go wrong, now imagine that being written to a hard disk, tape drive, etc.
--
Andy
The only person to have all his work done by Friday was Robinson Crusoe
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
