Build a Java App Server Foundation for Thick-Client Deployment
Web 2.0, rich Internet applications, and heavy JavaScript have become the latest rage. But why build a Web application that tries to look and act like a thick client when you can leverage a traditional J2EE/Web application server architecture to easily deploy an actual thick client?
by Stephen Lum
June 6, 2006
o one doubts the impact the Internet and its partner in crime the Web browser have had on the world. If you're like me, you happily check the news, the latest sport scores, or the value of your portfolio after a bad day on the NASDAQ through a Web browser. But Web applications have limitations due to their reliance on HTTP. As you would expect, the Web application world recognizes the weaknesses of the HTTP Web client and is trying to improve upon it with "Web 2.0" applications, Rich Internet Applications (RIA), AJAX, Lazlo, Flex, etc.
All of these technologies are attempts to bring a thick-client feel to thin Web clients. But in my assessment, chopping and painting a Volkswagen to make it feel like a Porsche will never make it drive like a Porsche. I'm not trying to start a Web client versus desktop application war; I think each has its purpose. But after spending lots of time developing with Dojo, script.aculo.us, AJAX, Prototype, etc., I feel that much of the Web 2.0 stuff is just a hack to circumvent HTTP's limiting request/response paradigm and ultimately to push HTTP to do more than it was intended to do.
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!