Gerbrand on ICT » ria

InfoQ, Tim Bray on the Future of the web

gerbrand — Tue, 24 Mar 2009 20:45:46 +0000

I often view or read the InfoQ, a site with articles on software development, programming. Almost all content they publish is very good. One I just saw was: Tim Bray on the Future of the web, an interview with someone of Sun. Interesting view has Tim on the web. He’s quite sceptical on RIA. Many ordinary users we’re quite glad when webapplications came – as they replaces often hard to use applications created using Visual Basic, VC++, Delphi and others with pull-down menu’s, ill-designs user interfaces. He also considers a bad thing if the back-button is disabled, many users find very relieving if they can go back once they’re confused. Gives you something to think about.
I don’t agree for entirely - they’re a lot of very good applications too, and there are quite confusing webapplications. But still, maybe for many applications he’s right.

Swing popularity rising

gerbrand — Sun, 15 Mar 2009 22:43:19 +0000

Years ago I developed several Swing application – most of them are still being used now. Later I switched to webapplication using http, javascript and html. I do like thinking about client-server communication, distributed software, databases and other parts of enterprise development. I never liked devoping client frameworks using any of the many webapplication frameworks like jsp/servlets, struts2, jsf. Somehow they never give the same ease of use. Usually it takes a lot more them having the application behave good, and still the GUI is slower and less responsive for the user. Even applicationd developed using advanced ajax frameworks like GWT are as good as application once written in Visual Basic or Delphi – considering a computer is now-a-days a whole lot faster.

Fortunately for developers Swing seems to be rising in popularity a lot. On Javaworld there are published articles on Swing, like this one on The Swing Cookbook, and on Dzone I found a weblog on Swing, or more specifically Java Desktop.
One of the reasons of the increasing popularity might by JSR 296, a standard for Swing. The standard is in development since 2006, but seems to be getting more attention lately. In a posting on JSR 296 and Swing suggests Swing might become obsolete – as Sun concerns- because of JavaFX. I don’t think (hope) Swing will disappear any time soon. Sun has a new architect on JSR 296 since last year, although there’s not that much progress on development or updates. On JSpring, a popular conference on Java in the Netherlands, there a session on JSR296, allthough Javapolis (now Devoxx) there was a talk on JSR-296 in 2006 already. I’ll be curious what will be told in that session.

Pattern in RIA

gerbrand — Sat, 17 Jan 2009 16:49:48 +0000

The Flex framework is getting more and more populair, and other similar RIA-frameworks as JavaFX and Sliverlight get a lot of attention. Some people see Flex as a alternative for webframeworks as Widget, JSF, Struts or GWT. However, there’s something fundementelly different. When program in Flex, you actually build a client-application. That application runs entirely on the client’s computers. The client connects to the server only when the client need information from the server. The client retrieves information via (web)services.

The pattern (as you can call it) is very unlike webframeworks, where the software runs mostly on the server. When a user accesses a webapplication, the webframework will generate html, javascript and xml and send that to the client’s webbrowser. The webframework also needs to create a (HTTP-)session along with a sessionid that is stored at the client-computer.
When a client performs some interaction, like pressing a button, a relatively complicated process is started: a javascript event or browser submit is emitted. The webframework will retrieve that event on the server using generated javascript- and html-code. Using the sessionid, the right user-session, containing client-data is loaded after which more automagic processes are performed.
You might wonder, what about Ajax ? The answer, with Ajax, or JQuery or other framework, the only advantage is, in case o a UI-event not the entire browserpage has to be reloaded and shown on the user, but only a part.

Not so long ago most enterprise software was developed as client-server: a client application would run on an users computer, while the server would consist of a database server. The client would make a connection to the database. The (business) logic of the software was contained in the application, while the database contained the data.
This development-model was quite easy for developers. I don’t have hard data, but I think the productivy was much higher back then. My guess is that, for many simple CRUD-like requirements, a average Visual Basic, Delphy, Clipper developer was a lot faster.
Of course one of the mayor problems back then, were the installation and maintance of the client computers. Webapplications pretty much solved that, as the only client software you had was the browser. Another problem is security: usually the client was connected with the server via a direct connection to the database. That means, if an unauthorized user would gain access to the client software he could do a lot of harm.
In webapplications, a user can only access the software by logging in the the webapplication. Without a username/passsword or other means of authentication, getting access to the server is very hard.

In modern RIA frameworks these problems are mostly solved. The software runs in a standardized plugin like the flash-player or java-player. That software is a lot easier to maintain then custom client software. A RIA-application accesses the server via a webservice. Fine-grained security can added accessed to the webservice, preventing unauthorized access. That way, access to the server/backend can be controlled.

All in all, modern RIA bring back productivity to the developer and the user. Developers finally don’t have to waste time learning yet another greatest framework (Struts, SpringMVC, JSF, ADF, GWT), and solving problems inherently part of webdevelopment (http-sessions, javascript debugging, html hell, generated code) . Users finally don’t have to wast time waiting for browser refreshes, loading times and timewasting slow operations.

For an overview on different RIA-frameworks, and more on this subject see: Rich Internet Applications: State of the Union . The term design pattern for RIA I got from the following presentation of a Adobe Evangelist on J-Fall ’08.