<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to 7: query mechanism should include PPD information</title><link>https://sourceforge.net/p/openprinting/feature-requests/7/</link><description>Recent changes to 7: query mechanism should include PPD information</description><atom:link href="https://sourceforge.net/p/openprinting/feature-requests/7/feed.rss" rel="self"/><language>en</language><lastBuildDate>Mon, 18 Apr 2005 18:14:59 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/openprinting/feature-requests/7/feed.rss" rel="self" type="application/rss+xml"/><item><title>query mechanism should include PPD information</title><link>https://sourceforge.net/p/openprinting/feature-requests/7/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The printer query mechanism available in the PAPI asks&lt;br /&gt;
the print&lt;br /&gt;
service for data and blindly sends it back the the&lt;br /&gt;
requestor.  For the&lt;br /&gt;
most part, this is fine, but In the case of the Solaris&lt;br /&gt;
LP IPP server&lt;br /&gt;
and the CUPS server, PPD files can be associated with&lt;br /&gt;
print queues&lt;br /&gt;
and the data can be retreived via IPP.  The IPP&lt;br /&gt;
implementation of&lt;br /&gt;
papiPrinterQuery() should make an attempt at retreiving and&lt;br /&gt;
digestings any associated PPD data to make it easier&lt;br /&gt;
for applications&lt;br /&gt;
to find out more about the printers, their queues and&lt;br /&gt;
their capabilities.&lt;br /&gt;
A comment in some mail that I received from dparsons at&lt;br /&gt;
debian dot org&lt;br /&gt;
prompted this.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Norm Jacobs</dc:creator><pubDate>Mon, 18 Apr 2005 18:14:59 -0000</pubDate><guid>https://sourceforge.net77eb26db2bf101ad617ee9f31e9219bdc229541b</guid></item></channel></rss>