<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: IPP browser</title>
	<atom:link href="http://cyberelk.net/tim/2007/09/27/ipp-browser/feed/" rel="self" type="application/rss+xml" />
	<link>http://cyberelk.net/tim/2007/09/27/ipp-browser/</link>
	<description></description>
	<pubDate>Mon, 06 Oct 2008 18:54:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: tim</title>
		<link>http://cyberelk.net/tim/2007/09/27/ipp-browser/#comment-413</link>
		<dc:creator>tim</dc:creator>
		<pubDate>Fri, 28 Sep 2007 09:18:57 +0000</pubDate>
		<guid isPermaLink="false">http://cyberelk.net/tim/2007/09/27/ipp-browser/#comment-413</guid>
		<description>Yes, ideally there would be no need to type in the host name.  We already try to take advantage of auto-discovery where possible.

There is CUPS browsing, but of course if you can discover printers that way you need not set explicit queues in the first instance.  The queue will already be set up, so you won't need to see the IPP Browser screen.

Another method is DNS-SD but I don't know that it's particularly well supported by printer devices.  In any case, we now ship Till Kamppeter's dnssd CUPS backend which can automatically discovery such queues.  I have just noticed that it deliberately filters out CUPS-hosted DNS-SD queues.  I'll find out why that is.

SNMP is another possibility but again, CUPS already provides SNMP browsing and so any identified queues should already have appeared in the list of devices (that first screenshot).

So really, you will only have to type in the host name if the auto-detection methods we use failed.  But once you've typed in the hostname we can carry on with auto-detection for queue names.</description>
		<content:encoded><![CDATA[<p>Yes, ideally there would be no need to type in the host name.  We already try to take advantage of auto-discovery where possible.</p>
<p>There is CUPS browsing, but of course if you can discover printers that way you need not set explicit queues in the first instance.  The queue will already be set up, so you won&#8217;t need to see the IPP Browser screen.</p>
<p>Another method is DNS-SD but I don&#8217;t know that it&#8217;s particularly well supported by printer devices.  In any case, we now ship Till Kamppeter&#8217;s dnssd CUPS backend which can automatically discovery such queues.  I have just noticed that it deliberately filters out CUPS-hosted DNS-SD queues.  I&#8217;ll find out why that is.</p>
<p>SNMP is another possibility but again, CUPS already provides SNMP browsing and so any identified queues should already have appeared in the list of devices (that first screenshot).</p>
<p>So really, you will only have to type in the host name if the auto-detection methods we use failed.  But once you&#8217;ve typed in the hostname we can carry on with auto-detection for queue names.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: APW</title>
		<link>http://cyberelk.net/tim/2007/09/27/ipp-browser/#comment-412</link>
		<dc:creator>APW</dc:creator>
		<pubDate>Fri, 28 Sep 2007 03:56:56 +0000</pubDate>
		<guid isPermaLink="false">http://cyberelk.net/tim/2007/09/27/ipp-browser/#comment-412</guid>
		<description>Hi Tim,

Nice progress.  This phrase caught my attention

Next, ***type in the hostname*** and click Find Queue…

Suggest that for a future version, you consider automating the discovery of the hostname.  I think that it's great that you're taking advantage of auto-discovery for the other parts of the process, but why not this one?  Rhetorical question.

Cheers,

Phil</description>
		<content:encoded><![CDATA[<p>Hi Tim,</p>
<p>Nice progress.  This phrase caught my attention</p>
<p>Next, ***type in the hostname*** and click Find Queue…</p>
<p>Suggest that for a future version, you consider automating the discovery of the hostname.  I think that it&#8217;s great that you&#8217;re taking advantage of auto-discovery for the other parts of the process, but why not this one?  Rhetorical question.</p>
<p>Cheers,</p>
<p>Phil</p>
]]></content:encoded>
	</item>
</channel>
</rss>
