<JavaScript Dilemma ⁄ >

In the last year or so the Ajax lifestyle has become common practice for Web development even in the developer mainstream after a few years where the technology was primarily treated as bleeding edge technology. Today however, Ajax is drifting more and more into the mainstream of Web development and you'd be hard-pressed to find a Web development tool that doesn't support it in some highly abstracted way.



Ajax is all about JavaScript and HTML DOM scripting and I thought in this column I'll review some of the approaches that are available to satisfy the requirements to build richer client applications and offer some thoughts on issues that I am struggling with as I compare the choices available for my own development and solutions that I work on with customers.



It's pretty clear that the days of hand coding most of the JavaScript to deal with client side logic are over. These days the complexity of what's happening on the client and the UI is quickly getting as complex if not more so than what's happening on the server. And while in the past we might have written a couple of lines of JavaScript here or there to validate forms, these days the requirements are much more involved. It's almost a foregone conclusion that the client side now also requires some sort of framework which is often completely decoupled from the server side.



este é só um excerto do artigo, para aceder ao artigo completo, clique no link em baixo:
this is just a small excerpt from the article, to access the full article please click in the link below:
http://west-wind.com/weblog/posts/84869.aspx