<?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: Typology of Rich Client technologies</title>
	<atom:link href="http://blog.frankel.ch/typology-of-rich-client-technologies/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.frankel.ch/typology-of-rich-client-technologies</link>
	<description>Nicolas Fränkel blog</description>
	<lastBuildDate>Wed, 08 Feb 2012 07:06:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: jbb</title>
		<link>http://blog.frankel.ch/typology-of-rich-client-technologies/comment-page-1#comment-528</link>
		<dc:creator>jbb</dc:creator>
		<pubDate>Sat, 30 Jan 2010 13:15:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.frankel.ch/?p=463#comment-528</guid>
		<description>Qooxdoo is a very interesting king of AJAX/client side framework.
It is the only one pure js pure client side.
I think DWR is not server agnostic and is not pure client side on your classification</description>
		<content:encoded><![CDATA[<p>Qooxdoo is a very interesting king of AJAX/client side framework.<br />
It is the only one pure js pure client side.<br />
I think DWR is not server agnostic and is not pure client side on your classification</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rinie</title>
		<link>http://blog.frankel.ch/typology-of-rich-client-technologies/comment-page-1#comment-527</link>
		<dc:creator>Rinie</dc:creator>
		<pubDate>Tue, 26 Jan 2010 07:45:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.frankel.ch/?p=463#comment-527</guid>
		<description>In my opinion Java / MVC approach is the wrong abstraction.
Rich clients should have three independent parts:
- Browser/Client interface
- Middleware
- Database/Storage

BrowserMiddleware are separate parts that communicate with HTTP/JSon preferably REST like.
SQL and Browser are familiar concepts, so should not be abstracted by GWT or ORM (or Corba or Soap).
Middleware should not do too much.

See WSGI, Rack and JSGI understand this (http://jackjs.org/jsgi-spec.html)
See also http://www.tbray.org/ongoing/When/201x/2010/01/02/Doing-It-Wrong

Objects should be used for complex compositions not to abstract http, html or database.
Applets were never a good user experience</description>
		<content:encoded><![CDATA[<p>In my opinion Java / MVC approach is the wrong abstraction.<br />
Rich clients should have three independent parts:<br />
- Browser/Client interface<br />
- Middleware<br />
- Database/Storage</p>
<p>BrowserMiddleware are separate parts that communicate with HTTP/JSon preferably REST like.<br />
SQL and Browser are familiar concepts, so should not be abstracted by GWT or ORM (or Corba or Soap).<br />
Middleware should not do too much.</p>
<p>See WSGI, Rack and JSGI understand this (<a href="http://jackjs.org/jsgi-spec.html" rel="nofollow">http://jackjs.org/jsgi-spec.html</a>)<br />
See also <a href="http://www.tbray.org/ongoing/When/201x/2010/01/02/Doing-It-Wrong" rel="nofollow">http://www.tbray.org/ongoing/When/201x/2010/01/02/Doing-It-Wrong</a></p>
<p>Objects should be used for complex compositions not to abstract http, html or database.<br />
Applets were never a good user experience</p>
]]></content:encoded>
	</item>
</channel>
</rss>

