From: Michael Sweet <mike@easysw.com>
To: "McDonald, Ira" <imcdonald@sharplabs.com>
Cc: printing-spool@freestandards.org,
'Norm Jacobs' <Norm.Jacobs@Sun.COM>,
"Hastings, Tom N" <hastings@cp10.es.xerox.com>,
"Zehler, Peter" <PZehler@crt.xerox.com>,
"'carl@manros.com'" <carl@manros.com>,
printing-architecture@freestandards.org,
'Harry Lewis' <harryl@us.ibm.com>
Subject: Re: [Printing-architecture] PAPI status report [IPP System Admin issue]
Date: Tue, 17 Feb 2004 11:33:38 -0500 [thread overview]
Message-ID: <40324262.5080108@easysw.com> (raw)
In-Reply-To: <CFEE79A465B35C4385389BA5866BEDF00C753E@mailsrvnt02.enet.sharplabs.com>
McDonald, Ira wrote:
> ...
> Michael Sweet - has CUPS implemented some/all of the IPP System
> Admin extension operations?
CUPS has implemented some of the operations (in most cases using
our own extension operations, since the CUPS ops came first) since
v1.0; here is a quick table:
Admin Spec Op CUPS Op
----------------------------------- -----------------------
Enable-Printer CUPS-Accept-Jobs
Disable-Printer CUPS-Reject-Jobs
Pause-Printer-After-Current-Job N/A *
Hold-New-Jobs N/A *
Release-Held-New-Jobs N/A *
Deactivate-Printer N/A
Activate-Printer N/A
Restart-Printer N/A
Shutdown-Printer N/A
Startup-Printer N/A
Reprocess-Job N/A **
Cancel-Current-Job Cancel-Job with job-id=0
Suspend-Current-Job N/A
Resume-Job N/A
Promote-Job N/A *
Schedule-Job-After N/A *
* = planned for future CUPS releases
** = planned for future CUPS releases, similar to Restart-Job
FWIW, the Hold-New-Jobs and Release-Held-New-Jobs operations are
somewhat problematic in the current definitions, since there is
no "job-admin-held" job-state-reasons value or "admin"
job-hold-until value to differentiate between a user-held job and
a job that is held via Hold-New-Jobs. That makes implementation
of Release-Held-New-Jobs somewhat challenging and makes it
impossible for an admin to know which jobs will be released.
In any case, the current spec covers both admin and operator
operations for both printers and jobs, so it might be useful
to break it up into functional documents published by the PWG
instead...
--
______________________________________________________________________
Michael Sweet, Easy Software Products mike at easysw dot com
Printing Software for UNIX http://www.easysw.com
next prev parent reply other threads:[~2004-02-17 16:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 15:57 [Printing-architecture] PAPI status report [IPP System Admin issue] McDonald, Ira
2004-02-17 16:33 ` Michael Sweet [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-17 17:38 McDonald, Ira
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40324262.5080108@easysw.com \
--to=mike@easysw.com \
--cc=Norm.Jacobs@Sun.COM \
--cc=PZehler@crt.xerox.com \
--cc=carl@manros.com \
--cc=harryl@us.ibm.com \
--cc=hastings@cp10.es.xerox.com \
--cc=imcdonald@sharplabs.com \
--cc=printing-architecture@freestandards.org \
--cc=printing-spool@freestandards.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.