<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: ITworks Design Journal: GWT RPC vs JSON</title>
	<atom:link href="http://binarymuse.net/2009/05/15/itworks-design-journal-gwt-rpc-vs-json/feed/" rel="self" type="application/rss+xml" />
	<link>http://binarymuse.net/2009/05/15/itworks-design-journal-gwt-rpc-vs-json/</link>
	<description>From the mind of a geek</description>
	<pubDate>Sat, 31 Jul 2010 20:44:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Paul S</title>
		<link>http://binarymuse.net/2009/05/15/itworks-design-journal-gwt-rpc-vs-json/comment-page-1/#comment-51</link>
		<dc:creator>Paul S</dc:creator>
		<pubDate>Mon, 22 Jun 2009 09:03:31 +0000</pubDate>
		<guid isPermaLink="false">http://binarymuse.net/?p=76#comment-51</guid>
		<description>Are you familiar with Spring? Given that this is your first introduction to using GWT with Tomcat I'm not sure that this suggestion is appropriate, but a good architecture for this project would be write all your server code agnostic of how it will be served, using Spring to cut through hard dependencies and make your code more modular. Then for the GWT stuff you'd use GWT-SL (server library) to export certain functionality as GWT-RPC "servlets" so your GWT app can talk to them using the same techniques that you see in the Hello World app that comes with GWT (nice and simple to use), and furthermore other things can interface with your server code too, like you could have a basic html version or a light version for mobile phone, etc, all plugging into the exact same server code. Elegant solution, but requires an all round knowledge of Java server programming, coupled with knowledge of GWT. When do we get to see the finished product? ;)</description>
		<content:encoded><![CDATA[<p>Are you familiar with Spring? Given that this is your first introduction to using GWT with Tomcat I&#8217;m not sure that this suggestion is appropriate, but a good architecture for this project would be write all your server code agnostic of how it will be served, using Spring to cut through hard dependencies and make your code more modular. Then for the GWT stuff you&#8217;d use GWT-SL (server library) to export certain functionality as GWT-RPC &#8220;servlets&#8221; so your GWT app can talk to them using the same techniques that you see in the Hello World app that comes with GWT (nice and simple to use), and furthermore other things can interface with your server code too, like you could have a basic html version or a light version for mobile phone, etc, all plugging into the exact same server code. Elegant solution, but requires an all round knowledge of Java server programming, coupled with knowledge of GWT. When do we get to see the finished product? ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ITworks Design Journal: GWT-RPC it is! &#171; BinaryMuse</title>
		<link>http://binarymuse.net/2009/05/15/itworks-design-journal-gwt-rpc-vs-json/comment-page-1/#comment-40</link>
		<dc:creator>ITworks Design Journal: GWT-RPC it is! &#171; BinaryMuse</dc:creator>
		<pubDate>Tue, 26 May 2009 16:17:52 +0000</pubDate>
		<guid isPermaLink="false">http://binarymuse.net/?p=76#comment-40</guid>
		<description>[...] Contact        &#171; ITworks Design Journal: GWT RPC vs JSON [...]</description>
		<content:encoded><![CDATA[<p>[...] Contact        &laquo; ITworks Design Journal: GWT RPC vs JSON [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BinaryMuse</title>
		<link>http://binarymuse.net/2009/05/15/itworks-design-journal-gwt-rpc-vs-json/comment-page-1/#comment-36</link>
		<dc:creator>BinaryMuse</dc:creator>
		<pubDate>Fri, 22 May 2009 22:49:35 +0000</pubDate>
		<guid isPermaLink="false">http://binarymuse.net/?p=76#comment-36</guid>
		<description>The issue is that the existing (RPC) interface is not available to outside services. It's also not stable--the GWT developers tweak with it from release to release to make it faster. So, if I implement an RPC solution, any other non-GWT apps would have to have a completely separate server-side solution.

I've actually made a decision--you'll see what it is shortly. :)</description>
		<content:encoded><![CDATA[<p>The issue is that the existing (RPC) interface is not available to outside services. It&#8217;s also not stable&#8211;the GWT developers tweak with it from release to release to make it faster. So, if I implement an RPC solution, any other non-GWT apps would have to have a completely separate server-side solution.</p>
<p>I&#8217;ve actually made a decision&#8211;you&#8217;ll see what it is shortly. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Morgan</title>
		<link>http://binarymuse.net/2009/05/15/itworks-design-journal-gwt-rpc-vs-json/comment-page-1/#comment-35</link>
		<dc:creator>Matthew Morgan</dc:creator>
		<pubDate>Tue, 19 May 2009 12:00:55 +0000</pubDate>
		<guid isPermaLink="false">http://binarymuse.net/?p=76#comment-35</guid>
		<description>For non-GWT stuff, what about making another server-side interface that takes GET/POST arguments and makes calls to your existing interface, then outputs XML or something similar?  You could treat the new interface as the view.  That would be a good test of how strong your MVC implementation is as well...if you can easily implement alternate views, that's a good sign.

Then again, I'm really new to a lot of this stuff.  I hope that made sense.  ;)</description>
		<content:encoded><![CDATA[<p>For non-GWT stuff, what about making another server-side interface that takes GET/POST arguments and makes calls to your existing interface, then outputs XML or something similar?  You could treat the new interface as the view.  That would be a good test of how strong your MVC implementation is as well&#8230;if you can easily implement alternate views, that&#8217;s a good sign.</p>
<p>Then again, I&#8217;m really new to a lot of this stuff.  I hope that made sense.  ;)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
