I have some clarifications to what Carl suggests. See TH>
From: kugler at us.ibm.com [mailto:kugler at us.ibm.com]
Sent: Wednesday, June 28, 2000 08:41
To: ipp at pwg.org
Subject: Re: IPP> Question concerning job-hold-until
--- In ipp at egroups.com, Michael Sweet <mike at e...> wrote:
> Hello, all!
>> I have a quick implementation question concerning the job-hold-until
> attribute, which doesn't seem to be addressed in the final model
> document for IPP/1.1.
>> Without going into too much detail, we have a customer that wants
> to know if the job-hold-until attribute should always be returned
> by a get-jobs or get-job-attributes request, or if it should only
> be returned if the job-hold-until attribute was specified for the
> job (at job creation or later with a hold-job request)
As a general rule, you should always return all applicable attributes, even
though some may contain 'unknown' or 'no-value' values. Otherwise it's
difficult for the client to determine which attributes you support.
TH> I agree that a Get-Job-Attributes or Get-Jobs should return all
requested attributes. However, if the attribute isn't supported at all, the
Printer SHOULD return it in the Unsupported Attributes group with the
'unsupported' out-of-band value, not in the Job Attributes group with
'unknown' or 'no-value' out-of-band value.
> If the latter, what happens when the hold condition expires (e.g.
> the job starts printing)? Do we change the value to "no-hold"?
I wouldn't change it.
TH> I agree.
> Similarly, if we always should send job-hold-until, do we send a
> value of "no-hold" or an "unknown" value tag?
The ?no-value? value is used for a supported attribute to which no value
has been assigned.
TH> I don't think a Get-Job-Attributes or Get-Jobs should return a value for
"job-hold-until", if the client omitted the attribute in the Job Creation
> Michael Sweet, Easy Software Products mike at e...> Printing Software for UNIX http://www.easysw.com