[cups.general] viewing jobs in distant queue

[Johannes Meixner]

Hello,

On Jun 1 09:49 Tim Waugh wrote (shortened):
> I wonder why the lpd backend doesn't hang around until the remote job
> has finished though?

>From a CUPS' backend point of view the "job" is usually
finished as soon as the recipient had accepted the last byte,
see for example
http://en.opensuse.org/SDB:CUPS_in_a_Nutshell
"The Backends"

> Couldn't it use the new back-channel data bits to
> communicate the job status?

This does not mean that one cannot make a backend which
uses the back-channel and waits until the recipient had
actually somehow finally processed the last byte of the job
but of course this means that it really waits until this
happens - i.e. no subsequent job for this queue would be
processed by CUPS until the backend had finished.

Assume a big and fat PostScript printer with tons of internal
memory and a lot of finishing stuff. It would be annoying
if the backend waits until the last page was actually printed,
sorted, folded, punched, and stapled until the final booklet
was ejected ;-)


Kind Regards
Johannes Meixner
-- 
SUSE LINUX Products GmbH, Maxfeldstrasse 5      Mail: jsmeix at suse.de
90409 Nuernberg, Germany                    WWW: http://www.suse.de/