[cups.general] Question re which-jobs

[Johannes Meixner]

Hello,

On Oct 1 08:41 Michael Sweet wrote (shortened):
> On Oct 1, 2010, at 5:43 AM, Johannes Meixner wrote:
>> ...
>> Of course a special backend could query the actual printer
>> and wait until the actual printer actually finished printing
>> but this would delay printing of subsequent jobs until the
>> previous job had actually finished printing.
>
> This is, in fact, what happens for IPP and AppSocket printing
> by default. Also, a driver can stick around and monitor the
> printer while it is printing, providing similar semantics.

But even then it still dpends on the software (firmware) running
inside the printer device what exactly it means when the printer's
software reports a job as "finished".

Additionally printing accounting software should provide
the same kind of information.
Perhaps printing accounting software is the most reliable
software which can report whether or not a job has actually
completed printing (i.e. whether or not all pages of a job
haven been actually printed succesfully by the printer).
But even printer accounting has its own kind of issues.
For example see the "socket backend pagecounting off by one" thread:
http://www.cups.org/newsgroups.php?gcups.general+T+Q%22socket+backend+pagecounting+off+by+one%22


Kind Regards
Johannes Meixner
-- 
SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany
AG Nuernberg, HRB 16746, GF: Markus Rex