attachment-0001
<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Oct 8, 2009, at 10:31 AM, Ira McDonald wrote:</div><blockquote type="cite"><div><blockquote type="cite">...</blockquote></div></blockquote><blockquote type="cite"><div><blockquote type="cite">ISSUE: OK that the Printer MUST ignore “jobs-ids” if “my-jobs” = ‘true’ is<br></blockquote><blockquote type="cite">supplied, rather than reject the request and return the<br></blockquote><blockquote type="cite">‘client-error-bad-request” status?<br></blockquote><blockquote type="cite"><br></blockquote><br><br><ira> Yes, OK - a legacy Printer wouldn't understand "job-ids" (in Get-Jobs)<br>and would ignore it, so the above is the right behavior.<br></ira><br></div></blockquote><div><br></div><div>I don't like doing this without some indication there is a problem. Returning client-error-conflicting-attributes is an alternate way to go without saying "bad request", or if we want to allow this (and ignore job-ids) then we should return successful-ok-ignored-or-substituted-attributes with job-ids in the unsupported group of the response.</div></div><div><br></div><div>Moreover, Cancel-Jobs is a NEW operation, so we should do it right.</div><div><br></div><div><blockquote type="cite"><div><blockquote type="cite">ISSUE: OK that the Printer MUST reject a request that does NOT specify a<br></blockquote><blockquote type="cite">list of jobs and does NOT specify “my-jobs” = ‘true’? What if the<br></blockquote><blockquote type="cite">requesting user is the operator? Should this case cancel all jobs?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">In other words, is it OK that the Cancel-Jobs operation does not allow the<br></blockquote><blockquote type="cite">Operator to cancel all jobs?<br></blockquote><blockquote type="cite"><br></blockquote><br><br><ira> Cancel-Jobs is NEW, so we can make it solid. Missing required<br>operation attributes must be a client error - it's NOT desirable that<br>Cancel-Jobs be able to cancel *all* jobs.<br></ira><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#144FAE"><br></font></font></div></blockquote><div><br></div>Huh? We *want* a way for an administrator to cancel all jobs without purging the job history. Otherwise there is no way to atomically cancel all jobs on a printer...</div><div><br><blockquote type="cite"><div><blockquote type="cite">ISSUE: OK that the Printer cancels the ones owned, but not the ones not<br></blockquote><blockquote type="cite">owned? Then the Printer can repeatedly perform Cancel-Job operations on<br></blockquote><blockquote type="cite">each job in the list, rather than checking the entire list before canceling<br></blockquote><blockquote type="cite">any<br></blockquote><blockquote type="cite"><br></blockquote><br><br><ira> No, bad choice. The Printer MUST immediately check that all members<br>of "job-ids" are owned by the end user (if not operator or admin requester),<br>so that it returns a privilege error and does NOT cancel ANY jobs.<br></ira><br></div></blockquote><div><br></div>Right, we agree here...</div><div><br></div><div><blockquote type="cite"><div><blockquote type="cite">ISSUES for the Get-Jobs enhancement:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">ISSUE: OK that the Printer MUST ignore “jobs-ids” if “my-jobs” = ‘true’ is<br></blockquote><blockquote type="cite">supplied, rather than reject the request and return the<br></blockquote><blockquote type="cite">‘client-error-bad-request” status?<br></blockquote><blockquote type="cite"><br></blockquote><br><br><ira> Yes, OK - this is compatibile with legacy Printers that don't understand<br>(and must ignore) "job-ids".<br></ira><br></div></blockquote><div><br></div>Same issue here as for Cancel-Jobs, but I am OK returning successful-ok-ignored-or-substituted-attributes since this is an existing operation.</div><div><br></div><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Monaco; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div>___________________________________________________</div><div>Michael Sweet, Senior Printing System Engineer</div><div><br></div></span><br class="Apple-interchange-newline">
</div>
<br><br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body></html>