Comment 8 for bug 187049

Regarding comment #6
https://bugs.launchpad.net/hplip/+bug/187049/comments/6
'With the udev solution any cups backend will work including the "usb" backend.'

Thanks to mention it!
This is THE reason to do firmware upload via udev.

Nevertheless:
The backend must still be fixed so that print jobs cannot get lost
if there is no firmware in the device and/or that there cannot happen
any mess when there are pending print jobs in the queue
while the device is power-cycled and additionally also that the job
is not lost when communication crashes while the job is sent
(e.g. because of power-cycle while the job is sent).

Imagine what normal users usually do if a particular printout is not
as expected (and when there are subsequent jobs in the queue
or if it is a longer job which is not yet sent completely to the device).
What else could they do except to power-cycle the device
when the only button/switch at the device is the power switch?
Many users don't know or do the CUPS "cancel".