Enterprise Ajax | Recently... | Elsewhere | Search | Login |
fancy

Enterprise Ajax

Strategies for Building High Performance Web Applications



Dave Johnson | Alexei White | Andre Charland

Build reliable, scalable, enterprise-class web applications with AJAX. Writing for enterprise developers, architects, and user-interface specialists, Johnson, White, and Charland explain why AJAX offers such great promise in large-scale development. Next, they systematically introduce key AJAX techniques and components. You'll walk through developing frameworks for building AJAX applications that combine data tables, web forms, charts, search, and filtering: the very systems business depend on in CRM, ERP, BI, and beyond. Then, building on this strong foundation, the authors identify proven AJAX architectural patterns, and present case studies drawn from actual .NET and Java AJAX applications.

categories


about this blog
This site is the living space for topics and discussion related to Enterprise Ajax, a book by Nitobi, and published by Pearson / Prentice Hall. Its also a blog for topics relating to AJAX development, including JavaScript, XSLT, XML, DHTML, PHP, Java, and ASP.NET.

continue reading this article

recently on this blog


fancy

Come get the source code.

3 09 2007

The source code for Enterprise Ajax is now available for download! Get it here:

Download the Source Code

categories Filled under: resources

fancy

Handling Millions (or billions) of records in the browser

24 07 2007

A reader on JavaRanch asks:

“How do I handle Million-Records-Fetching from the database and dumping it to the GUI?”

livescroll.gifMy preferred solution is to use LiveScrolling.

This essentially creates the illusion that all the records are loaded at once in the browser, but you are loading new records incrementally as the user moves down the recordset. This can be achieved easily using XmlHttp requests. You can combine this with a technique called Predictive Fetch to smooth the experience out for the user.

One key thing to remember, particularly if you are dealing with the millions of records use case, is that you will need to start tossing away records if they are not needed anymore to avoid filling up your stack - particularly if this means holding a lot of HTML on the page.

Check this out for an example of LiveScrolling: Nitobi CompleteUI demos.

categories Filled under: patterns







links elsewhere

monthly archives

search this place


login