I think the idea is that if you support a Job Template attribute (such as
job-hold-until) then you will return it when requested by a client. It
matter if the attribute wasn't specified at job creation, as the default
(job-hold-until-default) value will be used instead to set the attribute at
Michael Sweet <email@example.com>@pwg.org on 28-06-2000 16:17:09
Sent by: firstname.lastname@example.org
To: IPP Mailing List <email@example.com>
Subject: IPP> Question concerning job-hold-until
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)
If the latter, what happens when the hold condition expires (e.g.
the job starts printing)? Do we change the value to "no-hold"?
Similarly, if we always should send job-hold-until, do we send a
value of "no-hold" or an "unknown" value tag?
-- ______________________________________________________________________ Michael Sweet, Easy Software Products firstname.lastname@example.org Printing Software for UNIX http://www.easysw.com
This archive was generated by hypermail 2b29 : Wed Jun 28 2000 - 12:02:01 EDT