[IPP] Proposed Finishings 2.0 change: require "finishings-col-database" to not be returned by default - must be explicitly requested

[IPP] Proposed Finishings 2.0 change: require "finishings-col-database" to not be returned by default - must be explicitly requested

[IPP] Proposed Finishings 2.0 change: require "finishings-col-database" to not be returned by default - must be explicitly requested

Kennedy, Smith (Wireless Architect) smith.kennedy at hp.com
Mon Feb 1 21:25:13 UTC 2016


Hi there,

At HP Inc. we have observed a phenomenon with the "finishings-col-database" similar to the "media-col-database": it can be quite large, and including it in with the rest of the job template attributes for each Get-Printer-Attributes response can have a negative impact on response times.  Would it be reasonable or acceptable to make it so that "finishings-col-database" was withheld from Get-Printer-Attributes responses unless it was explicitly named in the "requested-attributes" attribute included in the IPP request?  The "finishings-col-ready" could be included by default, but no the full database.

We can discuss this in person next week but I wanted to front load the topic.  I wasn't prepared to mention it in today's slide review and didn't want it to belabor the slide review process.

Thanks for your thoughts,

Smith

/**
    Smith Kennedy
    Wireless Architect - Client Software - IPG-PPS
    Standards - IEEE ISTO PWG / Bluetooth SIG / Wi-Fi Alliance / NFC Forum / USB IF
    PWG Chair
    HP Inc.
*/





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20160201/0018c964/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4956 bytes
Desc: not available
URL: <http://www.pwg.org/pipermail/ipp/attachments/20160201/0018c964/attachment.p7s>


More information about the ipp mailing list