Part 1 - A brief history of the internet Flashcards
this splits the computing workload between:
* Client (front-end) - handles processing and displaying data
* Server (back-end) - handles processing and distributing data/content
how does a web application split computer workloads
describe the
content-length header
from a HTTP respoonse message
tells us the size of the returned file in the unit size defined in accept-ranges. Browsers can use this information to create progress bars in cases where data is downloaded
- invented by tim berners-lee
- Essentially runs on top of the internet but allows for requesting and sending information in a consistent manner
- Is comprised of the protocols HTTP, HTML
describe in 3 points the
world wide web
This gives the server additional information regarding our request
what are the header lines for in a HTTP GET request
what 5 things should be kept in mind when developing a web application
these include:
* Ensure the website is loaded as fast as possible
* Ensure users can easily find what they are looking for (usability)
* The web application is tested and delivered to schedule
* Built so that it can be maintained and expanded when needed
* Be scalable and responsive
tells us the size of the returned file in the unit size defined in accept-ranges. Browsers can use this information to create progress bars in cases where data is downloaded
describe the
content-length header
from a HTTP respoonse message
shows the date and time that the response message was created
describe the
date header
from a HTTP respoonse message
describe in 3 points the
world wide web
- invented by tim berners-lee
- Essentially runs on top of the internet but allows for requesting and sending information in a consistent manner
- Is comprised of the protocols HTTP, HTML
this is content that is changeable. the web application may keep track of
* Keep track of possibly thousands of items and customers
* Keep track of individual users
* Including there purchases
* There activity
describe
dynamic web content
what are the 3 parts that make up a HTTP GET request
this is made up of
* The request line
* One or more header lines
* Body or payload
what is
accessiblity
ensures that the web application can be used even by those who are physically or mentally disadvantaged
this tells the client what type of data they will be receiving
describe the
content-type header
from a HTTP respoonse message
describe the
request line
from a HTTP GET request
This lets the server know which resources we are interested in. It is made up of three parts separated by white space
GET / HTTP/1.1
how does a web application split computer workloads
this splits the computing workload between:
* Client (front-end) - handles processing and displaying data
* Server (back-end) - handles processing and distributing data/content
this is made up of
* The request line
* One or more header lines
* Body or payload
what are the 3 parts that make up a HTTP GET request
describe the
HTTP connection header
used by client and server and signifies whether the connection should stay open or not
describe the
last-modified header
from a HTTP respoonse message
details of when the resource was last modified. The browser may cache the resource with the timestamp so when it next accesses the resource if the timestamps are not to far in the past it will re use the already cached resource
is 6 points summarise what a web application should fullfil
- fulfils some form of ‘business’ requirement
- is built using internet and web technologies and protocols
- is delivered by distributed architecture
- is standards-compliant
- should be usable
- should be accessible.
this gives the server information about the user agent that is requesting the resources this can include info such as your OS and browser
describe the
HTTP user-agent header
- fulfils some form of ‘business’ requirement
- is built using internet and web technologies and protocols
- is delivered by distributed architecture
- is standards-compliant
- should be usable
- should be accessible.
is 6 points summarise what a web application should fullfil
describe the
content-type header
from a HTTP respoonse message
this tells the client what type of data they will be receiving
what 3 parts is a HTTP response message made up of
this is made up of:
* Status line
* Header lines
* Body
describe
hypertext transfer protocol (HTTP)
allows a client to request information from a server and the server reply to the request
this tells the server which type of resources we can accept. we may also set a priority on resources
describe the
HTTP accept header
used for caching purposes and validates that a locally cached resource is identical to the one stored on the server if so then the server will not send the resource and it can be found locally using the cached copy
describe the
ETag (Entity Tag) header
from a HTTP respoonse message
is part of the ranges system. The ranges system lets the client request only part of a file instead of having to download the whole file. This tells the client what unit size we are working with
describe the
accept-ranges header
from a HTTP respoonse message
describe the HTTP status codes beginning with 1, 2, 3, 4 and 5
1xx - this is information status codes
2xx - this is a success status code
3xx - this status code means that the resource has been moved and information of where it can be found may be given
4xx - this indicates a client error (404 code, which indicates that the requested resource was not found)
5xx - this indicates that there was a server side error
ensures that the web application can be used even by those who are physically or mentally disadvantaged
what is
accessiblity
allows a client to request information from a server and the server reply to the request
describe
hypertext transfer protocol (HTTP)
what is
usability
this ensures that the user interface is intuitive and unambiguous. essentially meaning that the user can easily navigate the web application and find what they are looking for
Born in 2004 works with the World Wide Web Consortium (W3C) in maintaining and evolving html and other technologies that are a fundamental part of a web platform
what is the
Web Hypertext Application Technology Working Group (WHATWG)
this is a web page that is unchanging and every client requesting it will see the same content. it does not take into account:
* Who you are
* Where your from
* When you visit
describe a
static web page