attachment
<div dir="ltr">I could see a desire to support job-release on lower end printers that wouldn't have enough memory to spool a job. However, I think this is undesirable from a service perspective as this will likely cause a print spooler to hang, waiting forever for the printing to start. However, what do we do if the printer "supports" spooling but the job is too large? This would require similar resolution (unless we reject those jobs).<div><br></div><div>Sean</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Dec 3, 2020 at 2:01 PM Kennedy, Smith (Wireless & IPP Standards) via ipp <<a href="mailto:ipp@pwg.org">ipp@pwg.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Greetings,<br>
<br>
>From our November 2020 F2F review*** of IPP Enterprise Printing Extensions v2.0, an unanswered question was whether the specification ought to require that the Printer spool the Job, and so restrict the Job Release feature to only those Printers that report 'spool' or 'automatic' for "job-spooling-supported", and if the Printer reports 'automatic', then it MUST spool Jobs that include the "job-release" Job Template attribute.<br>
<br>
Is there is a need to support Job Release on printers that cannot spool (store the Job before processing)?<br>
<br>
Thanks for any thoughts,<br>
<br>
Smith<br>
<br>
/**<br>
Smith Kennedy<br>
HP Inc.<br>
*/<br>
<br>
_______________________________________________<br>
ipp mailing list<br>
<a href="mailto:ipp@pwg.org" target="_blank">ipp@pwg.org</a><br>
<a href="https://www.pwg.org/mailman/listinfo/ipp" rel="noreferrer" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">Sean Kau</div></div>