Just read this and thought I'd recommend. He definitely prefers thick clients instead of Ajax.
It's pretty good; the next time I start a new project and use a thick client to app server, I'll definitely consider Spring Remoting based on this article. I can't believe how easy it is to switch protocols b/w rmi and http with no code change.
What I really like is that he's created a J2EE server, and shown the way for a thick client for the view instead of web pages.
-
A business component architecture with Spring 3.0/3.1 – Part 3: Properties
-
Tweaks to resolve xcache and fastcgi issue for socialengine
-
LoudCloud Systems Introduces First Fully Adaptive and Configurable Learning Management Systems
-
50 Open Source Tools That Could Help You Find (or Keep) a Valentine
-
Scripting for DB2 LUW – Why Perl?
-
Social Networking site just for Kids-Kidsocial
Add your comment
