topical media & game development
[] readme course(s) preface I 1 2 II 3 4 III 5 6 7 IV 8 9 10 V 11 12 afterthought(s) appendix reference(s) example(s) resource(s) _

talk show tell print

basic-ajax-10-ch10-examp2.htm / htm



  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
  <html xmlns="http://www.w3.org/1999/xhtml">
  <head>
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
  <title>Ajax Feed Reader</title>
  <link rel="stylesheet" href="feed.css" type="text/css" />
  <script type="text/javascript" src="feed.js"></script>
  </head>
  <body onload="sendRequest()">
  <div id="masthead">
    <h1 id="siteName">Beginning Ajax by Chris Ullman and Lucinda Dykes </h1>
  </div>
  <div id="content">
    <h2 id="pageName">Chapter 1  </h2>
    <div class="story">
      <h3>Introducing Ajax</h3>
      <p> History is littered with forks, branches and what-if’s. The pace of development of technology is relentless and often merciless. Past battles have seen VHS triumph over Betamax, PCs over microcomputers, Internet Explorer over Netscape Navigator and there’s plenty more similar conflicts just waiting to happen in DVD formats. It doesn’t mean that one technology was necessarily better than the other, it’s just that one format or technology had the features and functionality that was required at that time to make it more popular. You’ll still find enthusiasts now waxing lyrical about the benefits of  Betamax tape, claiming that it was smaller, had better quality and such like, it doesn’t mean they were wrong , perhaps a little sad and obsessive maybe, but beneath it all they had a point.</p>
    </div>
    <div class="story">
      <p> The evolution of the Internet has had its own such forks. One that continues to rumble on to this day is the so-called “fat-client” vs “thin-client” debate. Briefly put this is the choice between getting your browser to do most of the work as opposed to get a server at the other end to do the processing. Initially in the mid-90s it looked as if the “fat-client” ideology was going to win out.  The introduction of Internet Explorer 4 and Netscape Navigator 4 brought with them the advent of Dynamic HTML, which used scripting languages to alter pages so that you could drag and drop items or make menus appear and disappear without requiring a page refresh. However within a year there was a rush towards the “thin-client”, with the introduction of server-side technologies such as Active Server Pages and PHP. The client-side techniques still exist, but the model of current Internet and web page usage is broadly based upon server side method of “enter your data, send the page to the server and wait for a response” model. </p>
    </div>
  </div>
  <div class="feedResults">
  <form>
  <input type="button" value="Update Feed" name="update" id="update" />
  </form>
  <script type="text/javascript">
  var updateFeed = document.getElementById('update');
  updateFeed.onclick = sendRequest;
  </script>
  <div class="feedResults" id="displayResults">&nbsp;
  </div>
  <br />
  </body>
  </html>
[] readme course(s) preface I 1 2 II 3 4 III 5 6 7 IV 8 9 10 V 11 12 afterthought(s) appendix reference(s) example(s) resource(s) _

(C) Æliens 20/2/2008

You may not copy or print any of this material without explicit permission of the author or the publisher. In case of other copyright issues, contact the author.