<?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: Print job failure alerts</title>
	<atom:link href="http://cyberelk.net/tim/2008/02/29/print-job-failure-alerts/feed/" rel="self" type="application/rss+xml" />
	<link>http://cyberelk.net/tim/2008/02/29/print-job-failure-alerts/</link>
	<description></description>
	<pubDate>Tue, 14 Oct 2008 07:56:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Johan</title>
		<link>http://cyberelk.net/tim/2008/02/29/print-job-failure-alerts/#comment-1272</link>
		<dc:creator>Johan</dc:creator>
		<pubDate>Wed, 26 Mar 2008 01:40:13 +0000</pubDate>
		<guid isPermaLink="false">http://cyberelk.net/tim/2008/02/29/print-job-failure-alerts/#comment-1272</guid>
		<description>Wonderful, thank you.</description>
		<content:encoded><![CDATA[<p>Wonderful, thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tim</title>
		<link>http://cyberelk.net/tim/2008/02/29/print-job-failure-alerts/#comment-1093</link>
		<dc:creator>tim</dc:creator>
		<pubDate>Mon, 03 Mar 2008 09:15:20 +0000</pubDate>
		<guid isPermaLink="false">http://cyberelk.net/tim/2008/02/29/print-job-failure-alerts/#comment-1093</guid>
		<description>I've filed a &lt;a href="http://cups.org/str.php?L2732" rel="nofollow"&gt;separate bug report&lt;/a&gt; about this particular issue.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve filed a <a href="http://cups.org/str.php?L2732" rel="nofollow">separate bug report</a> about this particular issue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tim</title>
		<link>http://cyberelk.net/tim/2008/02/29/print-job-failure-alerts/#comment-1092</link>
		<dc:creator>tim</dc:creator>
		<pubDate>Mon, 03 Mar 2008 09:08:35 +0000</pubDate>
		<guid isPermaLink="false">http://cyberelk.net/tim/2008/02/29/print-job-failure-alerts/#comment-1092</guid>
		<description>&lt;a href="http://cups.org/str.php?L2352" rel="nofollow"&gt;This was the response&lt;/a&gt; I got when I mentioned this to the CUPS maintainer last though.</description>
		<content:encoded><![CDATA[<p><a href="http://cups.org/str.php?L2352" rel="nofollow">This was the response</a> I got when I mentioned this to the CUPS maintainer last though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tim</title>
		<link>http://cyberelk.net/tim/2008/02/29/print-job-failure-alerts/#comment-1085</link>
		<dc:creator>tim</dc:creator>
		<pubDate>Sun, 02 Mar 2008 18:33:26 +0000</pubDate>
		<guid isPermaLink="false">http://cyberelk.net/tim/2008/02/29/print-job-failure-alerts/#comment-1085</guid>
		<description>I hope so.  My idea is that the CUPS IPP backend should very closely follow the behaviour of the remote job.  This means keeping a local database mapping local job IDs to remote job URIs, and doing things like actually stopping the local job if the remote job has stopped, restarting the remote job if the local job is restarted, etc.</description>
		<content:encoded><![CDATA[<p>I hope so.  My idea is that the CUPS IPP backend should very closely follow the behaviour of the remote job.  This means keeping a local database mapping local job IDs to remote job URIs, and doing things like actually stopping the local job if the remote job has stopped, restarting the remote job if the local job is restarted, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johan</title>
		<link>http://cyberelk.net/tim/2008/02/29/print-job-failure-alerts/#comment-1079</link>
		<dc:creator>Johan</dc:creator>
		<pubDate>Sun, 02 Mar 2008 02:33:16 +0000</pubDate>
		<guid isPermaLink="false">http://cyberelk.net/tim/2008/02/29/print-job-failure-alerts/#comment-1079</guid>
		<description>Is there any way of fixing CUPS so that it does the right thing for remote jobs?</description>
		<content:encoded><![CDATA[<p>Is there any way of fixing CUPS so that it does the right thing for remote jobs?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
