Comment 9 for bug 75074

I think that it doesn't matter if you are pressing the CD eject button, or the power button, or your laptop battery is running out of charge, or whatever, isn't there some framework to inform applications that "resource X is going away within approximately Y to Z timeunit from now, there isn't anything you can do about that, act accordingly". And then the resource should just go away. And if an application didn't react to the notification, that's it's problem - no need to outright kill it, just force it to then handle the error it will get the next time it tries to use the resource - at which point it will hopefully be smart about things as well, like your CD burning software saying "hey, I was in the middle of copying that to another disc, put it back or that will fail [Try Again] [Fail]".