There are two new Job Template attributes: "banner-end" and "banner-start"
that CUPS/1.1 is introducing that I was curious about. It was our intention
that the IPP/1.0 "job-sheets" (type3 keyword | name) Job Template attribute
would perform the function that your two new Job Template attribute are
performing. While we only had two values defined in IPP/1.0 and IPP/1.1:
'none' and 'standard', we thought that it would be simple to add more values
whenever someone wanted.
In fact, the PWG "Production Printing Attributes, Set1" spec proposes three
new keywords for use with the IPP/1.1 "job-sheets" Job Template attribute:
job-start-sheet A job sheet MUST be printed to indicate the start of the
job-end-sheet A job sheet MUST be printed to indicate the end of the job.
job-wrap-sheets Job sheets MUST be printed to indicate the start and end of
all the output associated with the job.
Wouldn't it be simpler to use these values in CUPS, rather than introducing
two new Job Template attributes?
From your CUPS spec:
4.1.1 Print-Job Request
The following groups of attributes are supplied as part of the Print-Job
Group 1: Operation Attributes
Natural Language and Character Set:
The "attributes-charset" and "attributes-natural-language" attributes as
described in section 184.108.40.206 of the IPP Model and Semantics document.
The client MUST supply a URI for the specified printer.
Group 2: Job Template Attributes
(CUPS 1.1 and higher)
The client OPTIONALLY supplies a banner page that is printed after any files
in the print job. The name of "none" is reserved to indicate that no banner
page should be printed. If the client does not specify this attribute then
the value of the "banner-end-default" printer object attribute is used.
(CUPS 1.1 and higher)
The client OPTIONALLY supplies a banner page that is printed before any
files in the print job. The name of "none" is reserved to indicate that no
banner page should be printed. If the client does not specify this attribute
then the value of the "banner-start-default" printer object attribute is
Other Job Template Attributes
From: Michael Sweet [mailto:firstname.lastname@example.org]
Sent: Monday, March 13, 2000 05:44
To: IPP Mailing List
Subject: IPP> New CUPS 1.1 beta and set-job-attributes extension
We're getting close to the second beta release of CUPS 1.1. Part of
the next beta release is support for the set-job-attributes operation
The current implementation of the set-job-attributes in CUPS will
support changing of the job-printer-uri attribute, which is currently
marked as READ-ONLY in the spec. I've mentioned this problem before,
but let me summarize once again:
1. The job-printer-uri attribute needs to be changeable to
support a "move-job" type operation.
2. We can eliminate certain "special case" problems such as
moving jobs to a different server by restricting the new URIs
to the same server, or allowing the server to reject changes
if they are not possible (e.g. SHOULD support moving to a
different server, MUST support moving to a different printer
object on the same server...)
3. To support implementations that maintain a separate job ID
space for each printer object, the set-job-attributes
operation would then also report the current job-id and
job-uri attributes in the response data.
Our current options with CUPS are to ship it with a non-conforming
implementation of set-job-attributes,or register yet another
extension operation that performs exactly the same functionality
as set-job-attributes but allows the job-printer-uri attribute to
-- ______________________________________________________________________ Michael Sweet, Easy Software Products email@example.com Printing Software for UNIX http://www.easysw.com
This archive was generated by hypermail 2b29 : Mon Mar 20 2000 - 17:12:23 EST