[cups.general] Question re which-jobs

[Michael Sweet]

It actually is - IPP's "completed" state does not require that all pages have physically come out from the printer, just that they have all been processed.  High-end IPP printers often keep multiple jobs in flight...


On Oct 1, 2010, at 7:18 AM, John Dunn wrote:

> OK, thanks, so its not the same as the IPP which-jobs
> 
> 
> 
> 
>> 
>> Hello,
>> 
>> On Oct 1 03:52 John Dunn wrote (shortened):
>>> What does the lpstat which-jobs status of completed actually mean?
>>> Does it mean the job has physically completed printing?
>>> Or does it mean something else?
>> 
>> As far as I know it is as follows, see
>> http://en.opensuse.org/SDB:CUPS_in_a_Nutshell
>> ------------------------------------------------------------------
>> The print system considers the print job as completed when
>> the backend is finished. The backend is finished when the
>> transmission to the recipient is completed. If the further
>> processing at the recipient fails (e.g., if the printer
>> is not able to print the printer-specific data), this
>> will go unnoticed by the print system.
>> ------------------------------------------------------------------
>> 
>> 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.
>> 
>> 
>> Kind Regards
>> Johannes Meixner
>> --
>> SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany
>> AG Nuernberg, HRB 16746, GF: Markus Rex
>> 
> 
> _______________________________________________
> cups mailing list
> cups at easysw.com
> http://lists.easysw.com/mailman/listinfo/cups

________________________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair