Are there any advantages to setting synchronize=false? If the printer can
synchronize it may as well always synchronize, since nothing much is lost if
the job is simply discarded afterwards.
I think that many printers are likely to implement synchronization by
counting the number of sheets that have left the printer. In that case they
would prefer to always do a NPRO when shutting down, otherwise they would be
left with a number of unfinished sheets in the printer which complicates the
synchronization after a restart. Also, many printers, including web fed
printers, have to do a NPRO otherwise they will spoil the sheets that are
left in the machine.
I have the feeling that these attributes might not be used much. The
operator needs to choose whether to shut down, after all jobs, the current
job, the current copy of the current job or as soon as possible. In all
cases except the last the operator wants an NPRO. If a printer is shut down
mid-job, the operator would like not to do a NPRO if the printer can
synchronize afterwards, and an NPRO if not.
I work with high-end graphics printers, but things might be different in
other industries.
Anthony Porter
-----Original Message-----
From: owner-ipp at pwg.org [mailto:owner-ipp at pwg.org]On Behalf Of
kugler at us.ibm.com
Sent: 29 June 1999 22:37
To: Hastings, Tom N
Cc: alimpich at us.ibm.com; longstaf at us.ibm.com; ipp at pwg.org
Subject: RE: IPP> MOD - comments on Carl's Set and Admin operations
regist ration [some questions]
Tom wrote:
>Carl,
>>A couple of questions on your proposed operation attributes:
>>-----Original Message-----
>From: kugler at us.ibm.com [mailto:kugler at us.ibm.com]
>Sent: Wednesday, June 23, 1999 09:23
>To: ipp at pwg.org>Cc: hastings at cp10.es.xerox.com; alimpich at us.ibm.com; longstaf at us.ibm.com>Subject: Re: IPP> MOD - comments on Carl's Set and Admin operations
>registration pr
>>snip...
>>2) Rename "Backspace-Current-Job" to "Space-Current-Job" and add these
>OPTIONAL
> request operation attributes:
>>snip...
>>"non-process-run-out" (boolean) specifies whether the printer should
perform
>an
>NPRO (move the last printed sheet to the stacker) before restarting
>printing.
>An NPRO makes it easier to see exactly where the spacing took place.
>>TH1> What is the behavior if the client omits this attribute? The 'true'
or
>the 'false' behavior? (I hope it isn't implementation-dependent).
If unspecified, "non-process-run-out" defaults to 'false'.
>>TH2> What is the behavior if the implementation does not support this
>operation attribute? The 'true' or the 'false' behavior? (I hope it isn't
>implementation-dependent).
>>snip...
Hmmm. I don't know. I think this might be implementation dependent. This
attribute probably only has meaning for continuous-forms printers, if that
helps.
>>3) Add the following OPTIONAL operation attributes to the Shutdown-Printer
>request:
>"non-process-run-out" (boolean) specifies whether the printer should
perform
>an
>NPRO (move the last printed sheet to the stacker) before shutting down.
>>TH3> What is the behavior if the client omits this attribute? The 'true'
or
>the 'false' behavior? (I hope it isn't implementation-dependent).
If unspecified, "non-process-run-out" defaults to 'false'.
>>TH4> What is the behavior if the implementation does not support this
>operation attribute? The 'true' or the 'false' behavior? (I hope it isn't
>implementation-dependent).
I would guess that if the implementation doesn't support his attribute it
would
mean that it has no need for it, presumably because it always flushes the
end of
the last job. This would be the case for all printers except
continuous-forms
printers, right? Then, the behavior would be equivalent to
"non-process-run-out" == 'true'.
>>"synchronize" (boolean) specifies whether to synchronize the checkpoint
data
>for
>the current job with the pages that have actually printed. If this
>attribute is
>supported, a value of true implies that the Printer will be able to resume
>the
>job at the point of synchronization when restarted.
>>TH5> What is the behavior if the client omits this attribute? The 'true'
or
>the 'false' behavior? (I hope it isn't implementation-dependent).
If unspecified, "synchronize" defaults to 'false'.
>>TH6> What is the behavior if the implementation does not support this
>operation attribute? The 'true' or the 'false' behavior? (I hope it isn't
>implementation-dependent).
If the implementation doesn't support the attribute, it probably doesn't
support
the behavior, either. Therefore, 'false'.
>>snip...
>> -Carl
>