[cups.bugs] [HIGH] STR #2732: Status of remote IPP jobs cannot be discovered

[twaugh.redhat]

DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR New]

Currently it is impossible to know whether a job sent to a remote IPP queue
is actually still in progress, or if it failed.

The solution is for the IPP backend to act as a proxy for remote IPP jobs.
 It needs to maintain a small database of local job IDs to remote job URIs,
and to add the following actions:

1. While watching the remote job, if the remote job stops, fetch the
remote job-state-reasons and set them locally using an 'ATTR:' stderr
output line, and then exit with CUPS_BACKEND_STOP.

2. When the backend is started, if the job ID is already in the database,
try to restart the remote job (and re-submit the job if that fails) and
then continue to watch the remote job as normal.

This way, it will actually be possible to monitor the state of a remote
job.

(See http://cyberelk.net/tim/2008/02/29/print-job-failure-alerts/ for one
example of why this is needed: but otherwise just look at
http://localhost:631/jobs/ when a remote job has failed.)

Link: http://www.cups.org/str.php?L2732
Version: 1.3.6