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).
Sean
On Thu, Dec 3, 2020 at 2:01 PM Kennedy, Smith (Wireless & IPP Standards)
via ipp <ipp at pwg.org> wrote:
> Greetings,
>> 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.
>> Is there is a need to support Job Release on printers that cannot spool
> (store the Job before processing)?
>> Thanks for any thoughts,
>> Smith
>> /**
> Smith Kennedy
> HP Inc.
> */
>> _______________________________________________
> ipp mailing list
>ipp at pwg.org>https://www.pwg.org/mailman/listinfo/ipp>
--
Sean Kau
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20201207/c84c9c57/attachment.html>