Website Design

About This Presentation

Title:

Description:

Number of Views:45

Avg rating:3.0/5.0

Slides: 20

Provided by: scomH

Category:

Tags: design | trolleys | website

Transcript and Presenter's Notes

Title: Website Design

1
Website Design

2
Outline

3
Important information

4
Introduction to Module - Aims

To give the learner an in-depth understanding of
the role of different programming languages in
the design and development of server-driven web
environments.
To give the learner an in-depth understanding of
the role of databases in the design and
development of server-driven web environments.
To give the learner an in-depth appreciation of
both client- and server-side implications
associated with the delivery of database-driven
web applications.

5
Introduction to the Module - synopsis

This module builds on the Web Authoring module,
extending the range of skills and techniques
developed to include server-side scripting and
database integration.

6
Outline of the year

7
Assumed knowledge

8
Code

Static XHTML
Pages/data do not change without designer input
All users see the same page
Client side script (e.g. JavaScript)
Data still stays the same
Some customisation possible (e.g. colours, image
changes)
Validation of user input
Server side script (e.g. CGI, ASP, PHP,
ColdFusion)
Pages can be made on the fly based on variables
(e.g. search input, previous choices made by the
user on their last visit, inputs from other sites
or databases)
Page is constructed at the server end, then sent
as simple html to the client

9
How does it work? HTML

First consider an HTML page
You go to a webpage e.g. http//www.w3schools.com/
The browser goes and find w3schools.com
Once found it sends a request for the index.htm
file
The server finds that page and sends it to the
browser
Once received the browser looks at the HTML code,
reads it and converts it to a pretty, colourful,
but static page

10
How does it work? CGI

After HTML came CGI
HTML is one way (only receives), so something was
needed to send information back to the server.
forms and CGI (Common Gateway Interface) were
created
Forms used to get information from the user, then
that information is sent to the server where a
separate program is run to deal with it
Great for small apps like a guestbook, but
downside is every time someone sends something to
the server, a whole instance of the CGI program
is created. E.g. 5 people on site equals 5
programs running. Imagine if hundreds of people
wanted to connect at the same time?!?

11
How does it work? Server APIs

CGI too slow, so Server Application Programming
Interface born. ISAPI is the Microsoft version
Similar to CGI, ISAPI much more efficient.
Doesnt launch new version for every visitor

12
How does it work? ASP/PHP etc

And then came ASP/PHP/ColdFusion
Solved all the problems of CGI and ISAPI, and
they are simpler to learn and easier to use
CGI and ISAPI written in Perl or C
ASP/PHP/CFM simply write code in the HTML, side
by side
As with JavaScript

13
How does it work? ASP/PHP etc

You go to a webpage e.g. www.mydomain.com/index.ph
p
The browser goes and find mydomain.com
Once found it sends a request for the index.php
file
The server finds that page and executes it, which
means it looks through the pages and runs any
code in the page
After the code has run, all asp/php is removed
from the result (so people cannot steal it)
leaving a pure HTML page
The HTML page is sent to the browser for rendering