> I dunno about going on - It could potentially make for a dangerous > situation on the client-side. Consider if it missed an=20 > important update > that caused a lot of other things to fail to update. I think exiting > with a more graceful error makes a lot more sense than continuing and > ignoring the problem. I agree. I've had situations where a single file got corrupted while downloading (usually 0 length). I'd rather see an error message. Eric.
