Static web page - Objectives: Students will be able to

Static web page
From Wikipedia, the free encyclopedia
|
This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. (February 2008) (Learn how and when to remove this template message)
|
Static web page: is delivered to the user exactly as stored.
A static web page (sometimes called a flat page/stationary page) is a web page that is delivered to the user exactly as stored, in contrast to dynamic web pages which are generated by a web application.
Consequently, a static web page displays the same information for all users, from all contexts, subject to modern capabilities of a web server to negotiate content-type or language of the document where such versions are available and the server is configured to do so.
Static web pages are often HTML documents stored as files in the file system and made available by the web server over HTTP (nevertheless URLs ending with ".html" are not always static). However, loose interpretations of the term could include web pages stored in a database, and could even include pages formatted using a template and served through an application server, as long as the page served is unchanging and presented essentially as stored.
Static web pages are suitable for the contents that never or rarely need to be updated. However, maintaining large numbers of static pages as files can be impractical without automated tools. Any personalization or interactivity has to run client-side, which is restricting.
Advantages of a static website:
Quick to develop
Cheap to develop
Cheap to host
Disadvantages of a static website:
Requires web development expertise to update site
Content can get stagnant
Dynamic web page
From Wikipedia, the free encyclopedia
|
[hide]This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)
This article includes a list of references, related reading or external links, but its sources remain unclear because it lacks inline citations. (December 2012)
|
This article needs attention from an expert in Internet. The specific problem is: inline citations.
|
|
Dynamic web page: example of server-side scripting (PHP and MySQL).
A server-side dynamic web page is a web page whose construction is controlled by an application server processing server-side scripts. In server-side scripting, parametersdetermine how the assembly of every new web page proceeds, including the setting up of more client-side processing.
A client-side dynamic web page processes the web page using HTML scripting running in the browser as it loads. JavaScript and other scripting languages determine the way the HTML in the received page is parsed into the Document Object Model, or DOM, that represents the loaded web page. The same client-side techniques can then dynamically update or change the DOM in the same way.
A dynamic web page is then reloaded by the user or by a computer program to change some variable content. The updating information could come from the server, or from changes made to that page's DOM. This may or may not truncate the browsing history or create a saved version to go back to, but a dynamic web page update using Ajaxtechnologies will neither create a page to go back to, nor truncate the web browsing history forward of the displayed page. Using Ajax technologies the end user gets one dynamic page managed as a single page in the web browserwhile the actual web content rendered on that page can vary. The Ajax engine sits only on the browser requesting parts of its DOM, the DOM, for its client, from an application server.
DHTML is the umbrella term for technologies and methods used to create web pages that are not static web pages. Client-side-scripting, server-side scripting, or a combination these make for the dynamic web experience in a browser.
The basic idea of layers of abstraction – that each layer relies on those below it, but uses them “abstractly” that’s enough.
Put differently, higher-level layers depend on the functionality of lower-level layers, without worrying about precisely how those layers work. The Enduring Understanding from the CSP framework states: “6.1 The Internet is a network of autonomous systems” And these layers of abstraction (protocols) is a large part of what that statement is about.
|