<?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: Blogging from the GWT Conference: GWT as a Replacement for Java Swing Apps</title>
	<atom:link href="http://www.pathf.com/blogs/2007/12/blogging-from-t/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pathf.com/blogs/2007/12/blogging-from-t/</link>
	<description>Running commentary about agile development, user experience design and Ajax.</description>
	<pubDate>Fri, 05 Dec 2008 18:01:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: pohl</title>
		<link>http://www.pathf.com/blogs/2007/12/blogging-from-t/#comment-199</link>
		<dc:creator>pohl</dc:creator>
		<pubDate>Wed, 12 Dec 2007 22:33:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=176#comment-199</guid>
		<description>&lt;p&gt;Ken, I think a good answer to your question is that the vendors of these devices would &lt;br /&gt;
build a little HTTP daemon into the device.  To administer your router, you would point&lt;br /&gt;
your browser at port 8080 of the device's interface.  The dynamic 'gui' would run in your&lt;br /&gt;
browser, but anything that needed to talk to the hardware itself would happen on the&lt;br /&gt;
server side, over some service written using GWT's RPC mechanism, etc.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Ken, I think a good answer to your question is that the vendors of these devices would <br />
build a little HTTP daemon into the device.  To administer your router, you would point<br />
your browser at port 8080 of the device&#8217;s interface.  The dynamic &#8216;gui&#8217; would run in your<br />
browser, but anything that needed to talk to the hardware itself would happen on the<br />
server side, over some service written using GWT&#8217;s RPC mechanism, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken</title>
		<link>http://www.pathf.com/blogs/2007/12/blogging-from-t/#comment-198</link>
		<dc:creator>Ken</dc:creator>
		<pubDate>Mon, 10 Dec 2007 15:09:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=176#comment-198</guid>
		<description>&lt;p&gt;Very interesting. Makes sense in general but how could "desktop administration applications that manage their hardware" run in a browser since don't they need to access the hardware in ways that a browser can't?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Very interesting. Makes sense in general but how could &#8220;desktop administration applications that manage their hardware&#8221; run in a browser since don&#8217;t they need to access the hardware in ways that a browser can&#8217;t?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
