Tutorial eBooks PDF File Download

GUI business applications presented lower runtime costs than the CICSapplications they replaced due toreduced demand on the mainframeserver. This fat client would handle allbusiness logic and data validation andthen commit data to the server. The emergence of Java and the Web, however, prompted another major shift inthinking about building applications. WithInternet-based technology, suddenly com-panies could extend their reach by deliver-ing dynamic HTML in a browser to anyonewith a Web connection. This new Web-enabled world thus reversed the earliertrend, and application development beganmoving business logic back to the server. Many early adopters among the Fortune 500 migrated their legacy appli-cations to a J2EE architecture, attracted tothis emerging paradigm by the ease ofdeployment afforded by browser-baseddelivery of the presentation layer. For asignificant number of these companies,however, the strategy backfired, as theyincreasingly ran up against the usabilitylimitations of HTML, particularly formore complex GUI workflow, businesscalculations, or sophisticated graphics.What’s more, browser-based front endsintroduced performance inefficiencies asthe application must make round-trips tothe server to paint new views, a processthat can be cumbersome because of thebrowser’s inherent limitations in window-ing and real-time graphics capabilities.