Teknologi Maklumat dalam

Pendidikan

(BBD 10803)

TOPIC 8:
INTERNET AND WORLD WIDE WEB
 Topic Learning Outcomes

At the end of this topic, students should be able to:

1. Define the evaluation of internet
2. Define the term “Internet”
3. Discuss the concept of The World Wide Web concisely
4. Discuss the concept of Cloud Computing clearly
5. Discuss the concept of Fog Computing briefly
 8.1 Evolution of internet

Origins of the Internet

 The Internet started as an experiment in the late 1960s by

the Advanced Research Projects Agency (ARPA, now called
DARPA).
 DARPA experimented with the connection of computer
networks by giving grants to multiple universities and
private companies to get them involved in the research.
 Six Phases of Change of the Internet

Evolution Year Explanation

1st Phase Before Birth of ARPANET for the purposes of research and
1969 computer resource sharing in the US only. Most users
were scientists, students and academicians. The
Internet was used as a tool for sharing computer
resources.
2nd Phase 1970–1990 Communication like e-mail, File Transfer Protocol and
Usenet were used widely. Usage was still confined to
universities and government agencies. Internet usage
concentrated in the US, Europe and Japan. The
Internet was used as a tool of communication.
3rd Phase 1990–1997 Hypertext technique was used widely in network
information. The Internet began to attract public
attention because the Internet browser had attractive
and user-friendly interfaces.
 Six Phases of Change of the Internet

Evolution Year Explanation

4th Phase 1997–2000 The Internet explosion. The number of users
expanded rapidly. The Internet was used for business
transactions. It became the subject of conversations
and many articles regarding the Internet were written
in various magazines.
5th Phase 2001–2017 The Internet reality. Many dotcom companies closed
down. Realities of Internet advantages and
disadvantages were felt. Some initiatives to improve
the Internet continued.
6th Phase 2017- The Internet of Things refers to the ever-growing
onwords network of physical objects that feature an IP
address for internet connectivity, and the
communication that occurs between these objects and
other Internet-enabled devices and systems.
 Internet Timeline and Events
Year Event

1969 Four computers were connected on the ARPANET network in US. The
computers were from University of California, Los Angeles; University of
California, Santa Barbara; Stanford Research Institute and University of
Utah.
1971 The number of computers in the ARPANET was up to 21. A technique of
e-mail communication was introduced.
1973 The University College of London was connected to ARPANET, the first
connection of ARPANET outside the US.
1978 Transmission Control Protocol/Internet Protocol data sharing technique
was produced.
1979 Usenet was introduced. It involved two computers in ARPANET.
1982 ARPANET used Transmission Control Protocol/Internet Protocol
completely. Definitions of Internet and intranet were introduced.
Internet refers to the (worldwide) grouping of computer networks that
uses Transmission Control Protocol/Internet Protocol while intranet
refers to a computer network that uses Internet Protocol.
 Internet Timeline and Events
Year Event

1984 The number of computers on the Internet exceeded 1,000 units.

1988 The Internet was massively attacked by the Internet worms which were
computer software that spread on their own. This incident shows the low
level of safety on the Internet. Computer Emergency Response Team
(CERT) was set up to monitor security on the Internet.
1989 The number of computers exceeded 100,000 units. A book entitled
Cuckoo Nest was published. This book explained on how a group of
invaders from Germany were successful in entering some of the US
military computers without permission, via the Internet.
1990 ARPANET was terminated and replaced by National Science Foundation
Network network.
1991 Hypertext Transfer Protocol was produced by Tim Berners-Lee at CERN.
This became the basis for the development of the web on the Internet.
1992 The number of computers on the Internet exceeded 1 million units.
Malaysia also joined the Internet. The Internet network in Malaysia is
managed by Malaysian Institute of Microelectronic Systems (MIMOS).
 Internet Timeline and Events
Year Event
1996 Browser war between Netscape Communicator and Internet Explorer.
At that time, almost 80% of users were using Netscape.
1997 The backbone function of National Science Foundation Network for
the
provision of Internet passage was taken over by a commercial
company. A computer programming language based on objects –
Java, was launched by Sun Microsystem in 23 May 1997. This
language received extraordinary responses. Java enables websites to
have various attractive animations. Search engines were also
introduced. There were already 17,618 discussion forums based on
emails.
1998 The Internet was estimated to have millions of websites. Electronic
commerce (e-commerce) and portal technology began to attract
attention.
1999 The number of computers on the Internet was estimated at 76 million
units. The number of web servers was estimated at seven million
units.
2000 An estimated about one billion websites were on the Internet.
 Internet Timeline and Events
Year Event
2005 The world summit on the information society, held in Tunis,
established the internet governance forum to discuss internet related
issues (Web 1.0).
2007 In a article in June 2007 the combined weight of all the electrons
moved within the internet in a day is 0.2 millionths of an ounce (Web
2.0).
2009 Are more faster internet is created and the pro upgrade the old
websites
2015 Web 3.0 is slated to be the new paradigm in web interaction and will
mark a fundamental change in how developers create websites, but
more importantly, how people interact with those websites.
2017 - Web 4.0 – “Mobile Web”. The next step is not really a new version,
now but is a alternate version of what we already have. Web needed to
adapt to it’s mobile surroundings. Web 4.0 connects all devices in the
real and virtual world in real-time.
Internet Timeline
 Internet of Things (IoT)

 Internet of Things (IoT), cloud computing and service are

all aspects of a future internet
- Strengths of each can and should be combined
 Examples of successful combinations exist
- Both in the public and the business domain
 We are the beginning of an interesting journey
- many challenges still lie ahead
How IoT works?
 8.2 The internet

 Definition: The Internet is a grouping of computer networks that

is very large and covers the whole world. It operates using
Transmission Control Protocol/Internet Protocol (TCP/IP).
Internet versus Intranet
Internet versus Extranet
 8.3 The World Wide Web

The World Wide Web, commonly known as the Web, is

an information space where documents and other web
resources are identified by Uniform Resource
Locators, which may be interlinked by hypertext, and
are accessible over the Internet.
 8.3 World Wide Web

 The World Wide Web (abbreviated as the Web or WWW)

is a system of Internet servers that supports hypertext to
access several Internet protocols on a single interface
 The World Wide Web consists of files, called pages or
home pages, containing links to documents and
resources throughout the Internet.
 This includes e-mail, FTP, Telnet, and Usenet News. In
addition to these, the World Wide Web has its own
protocol: HyperText Transfer Protocol, or HTTP
 Programming languages such as Java, JavaScript, Visual
Basic, Cold Fusion and XML are extending the
capabilities of the Web
 WWW Background
19

 1989-1990 – Tim Berners-Lee invents the World

Wide Web at CERN
 Means for transferring text and graphics simultaneously
 Client/Server data transfer protocol
 Communication via application level protocol
 System ran on top of standard networking infrastructure

 Text mark up language

 Not invented by Bernes-Lee
 Simple and easy to use
 Requires a client application to render text/graphics

CS 640
 WWW History
20 contd.
 1994 – Mark Andreesen invents MOSAIC at National Center
for Super Computing Applications (NCSA)
 First graphical browser
 Internet’s first “killer app”
 Freely distributed
 Became Netscape Inc.
 1995 (approx.) – Web traffic becomes dominant
 Exponential growth
 E-commerce
 Web infrastructure companies
 World Wide Web Consortium

 Reference: “Web Protocols and Practice”, Krishnamurthy

and Rexford

CS 640
 WWW Components
21

 Structural Components
 Clients/browsers – to dominant implementations

 Servers – run on sophisticated hardware

 Caches – many interesting implementations

 Internet – the global infrastructure which facilitates data transfer

 Semantic Components
 Hyper Text Transfer Protocol (HTTP)

 Hyper Text Markup Language (HTML)

 eXtensible Markup Language (XML)
 Uniform Resource Identifiers (URIs)

CS 640
 Quick Aside – Web server use
22

Source: Netcraft Server Survey, 2001

CS 640
 WWW Structure
23

 Clients use browser application to send URIs via HTTP to

servers requesting a Web page
 Web pages constructed using HTML (or other markup
language) and consist of text, graphics, sounds plus
embedded files
 Servers (or caches) respond with requested Web page
 Or with error message
 Client’s browser renders Web page returned by server
 Page is written using Hyper Text Markup Language (HTML)
 Displaying text, graphics and sound in browser
 Writing data as well

 The entire system runs over standard networking protocols

(TCP/IP, DNS,…)
CS 640
 Uniform Resource Identifiers
24

 Web resources need names/identifiers – Uniform

Resource Identifiers (URIs)
 Resource can reside anywhere on the Internet
 URIs are a somewhat abstract notion
 A pointer to a resource to which request methods can be
applied to generate potentially different responses
 A request method is eg. fetching or changing the object
 Instance: http://www.foo.com/index.html
 Protocol, server, resource

 Most popular form of a URI is the Uniform Resource

Locator (URL)
 Differences between URI and URL are beyond scope
 RFC 2396

CS 640
 HTTP Basics
25

 Protocol for client/server communication

 The heart of the Web
 Very simple request/response protocol
 Client sends request message, server replies with response message
 Stateless
 Relies on URI naming mechanism
 Three versions have been used
 09/1.0 – very close to Berners-Lee’s original
 RFC 1945 (original RFC is now expired)
 1.1 – developed to enhance performance, caching, compression
 RFC 2068
 1.0 dominates today but 1.1 is catching up

CS 640
 HTTP Request Messages
26

 GET – retrieve document specified by URL

 PUT – store specified document under given URL
 HEAD – retrieve info. about document specified by
URL
 OPTIONS – retrieve information about available
options
 POST – give information (eg. annotation) to the server
 DELETE – remove document specified by URL
 TRACE – loopback request message
 CONNECT – for use by caches
CS 640
 HTTP Request Format
27

request-line ( request request-URI HTTP-version)

headers (0 or more)
<blank line>
body (only for POST request)

 First type of HTTP message: requests

 Client browsers construct and send message

 Typical HTTP request:

 GET http://www.cs.wisc.edu/index.html HTTP/1.0

CS 640
 HTTP Response Format
28

status-line (HTTP-version response-code response-phrase)

headers (0 or more)
<blank line>
body

 Second type of HTTP message: response

 Web servers construct and send response messages

 Typical HTTP response:

 HTTP/1.0 301 Moved Permanently

Location: http://www.wisc.edu/cs/index.html

CS 640
 HTTP Response Codes
29

 1xx – Informational – request received, processing

 2xx – Success – action received, understood,
accepted
 3xx – Redirection – further action necessary
 4xx – Client Error – bad syntax or cannot be
fulfilled
 5xx – Server Error – server failed

CS 640
 HTTP Headers
30

 Both requests and responses can contain a variable

number of header fields
 Consists of field name, colon, space, field value
 17 possible header types divided into three categories
 Request
 Response
 Body

 Example: Date: Friday, 27-Apr-01 13:30:01 GMT

 Example: Content-length: 3001

CS 640
 HTML Example
31

<HTML>
<HEAD>
<TITLE> PB’s HomePage </TITLE>
</HEAD>
<BODY>
<CENTER><IMG SRC = “bad_picture.gif” ALT = “ “><BR></CENTER>
<P><CENTER><H1>UW Computer Science Department</H1></CENTER>
Welcome to my goofy HomePage!
…
<A HREF = http://www.cs.wisc.edu/~pb/mydogs_page.html> Spot’s Page </A>
</BODY>
</HTML>

CS 640
 Example of WWW Apps

 Email→Electronic mail, or e-mail, allows computer

users locally and worldwide to exchange messages.
Each user of e-mail has a mailbox address to which
messages are sent. Messages sent through e-mail can
arrive within a matter of seconds.

 Telnet→Telnet is a program that allows you to log

into computers on the Internet and use online
databases, library catalogs, chat services, and more.
There are no graphics in Telnet sessions, just text.
7.4 What is Cloud computing ?

PROPERTIES AND CHARACTERISTICS

 7.4 Cloud computing

 Cloud computing is a model for enabling convenient,

on-demand network access to a shared pool of
configurable computing resources (e.g., networks,
servers, storage, applications, and services)
[Mell_2009], [Berkely_2009].
 It can be rapidly provisioned and released with
minimal management effort.
 It provides high level abstraction of computation
and storage model.
 It has some essential characteristics, service
models, and deployment models.
 What It Provides
35

 Cloud computing provides shared services as

opposed to local servers or storage resources
 Enables access to information from most web-
enabled hardware
 Allows for cost savings – reduced facility,
hardware/software investments, support

35
 Essential Characteristics
36

 On-Demand Self Service:

 A consumer can unilaterally provision computing
capabilities, automatically without requiring human
interaction with each service’s provider.
 Heterogeneous Access:
 Capabilities are available over the network and accessed
through standard mechanisms that promote use by
heterogeneous thin or thick client platforms.
 Essential Characteristics (cont.)
37
 Resource Pooling:
 The provider’s computing resources are pooled to serve
multiple consumers using a multi-tenant model.
 Different physical and virtual resources dynamically
assigned and reassigned according to consumer demand.
 Measured Service:
 Cloud systems automatically control and optimize
resources used by leveraging a metering capability at
some level of abstraction appropriate to the type of
service.
 It will provide analyzable and predictable
computing platform.
 Service Models
38

 Cloud Software as a Service (SaaS):

 The capability provided to the consumer is to use the
provider’s applications running on a cloud infrastructure.
 The applications are accessible from various client
devices such as a web browser (e.g., web-based email).
 The consumer does not manage or control the underlying
cloud infrastructure including network, servers,
operating systems, storage,…
 Examples: Caspio, Google Apps, Salesforce,
Nivio, Learn.com.
 Service Models (cont.)
39

 Cloud Platform as a Service (PaaS):

 The capability provided to the consumer is to deploy
onto the cloud infrastructure consumer-created or
acquired applications created using programming
languages and tools supported by the provider.
 The consumer does not manage or control the
underlying cloud infrastructure.
 Consumer has control over the deployed applications
and possibly application hosting environment
configurations.
 Examples: Windows Azure, Google App.
 Service Models (cont.)
40

 Cloud Infrastructure as a Service (IaaS):

 The capability provided to the consumer is to provision
processing, storage, networks, and other fundamental
computing resources.
 The consumer is able to deploy and run arbitrary software,
which can include operating systems and applications.
 The consumer does not manage or control the underlying
cloud infrastructure but has control over operating systems,
storage, deployed applications, and possibly limited control
of select networking components (e.g., host firewalls).
 Examples: Amazon EC2, GoGrid, iland, Rackspace
Cloud Servers, ReliaCloud.
 Service Models (cont.)
41

Service Model at a glance: Picture From http://en.wikipedia.org/wiki/File:Cloud_Computing_Stack.svg

 7.5 Fog computing

 Fog computing or fog networking is an architecture

that uses one or a collaborative multitude of end-
user clients or near user edge devices to carry out a
substantial amount of storage (rather than Stored
primarily in cloud data centers),
 communication (rather than routed over the internet
backbone), and control, configuration, measurement
and management (rather than controlled primarily by
network gateways such as those in the LTE (telecom
munication) core).
Fog computing is a decentralized computing
infrastructure in which data, compute, storage and
applications are located somewhere between the data
source and the cloud. Like edge computing, fog
computing brings the advantages and power of the
cloud closer to where data is created and acted upon
Example of Fog Computing
 How Does Fog Work?

 While edge devices and sensors are where data is generated and
collected, they don't have the compute and storage resources to
perform advanced analytics and machine-learning tasks. Though cloud
servers have the power to do these, they are often too far away to
process the data and respond in a timely manner. In addition, having
all endpoints connecting to and sending raw data to the cloud over the
internet can have privacy, security and legal implications, especially
when dealing with sensitive data subject to regulations in different
countries.
 It is important to note that fog networking complements -- not replaces
-- cloud computing; fogging allows for short-term analytics at the edge,
and the cloud performs resource-intensive, longer-term analytics.
Popular fog computing applications include smart grid, smart
city, smart buildings, vehicle networks and software-defined networks.
 Developers either port or write IoT applications for
fog nodes at the network edge. The fog nodes closest
to the
 network edge ingest the data from IoT devices.
Then—and this is crucial—the fog IoT application
directs different
 types of data to the optimal place for analysis, as
shown in Table 1:
 ● The most time-sensitive data is analyzed on the fog node closest to
the things generating the data. In a Cisco Smart Grid distribution
network, for example, the most time-sensitive requirement is to verify
that protection and control loops are operating properly. Therefore, the
fog nodes closest to the grid sensors can look for signs of problems and
then prevent them by sending control commands to actuators.
 ● Data that can wait seconds or minutes for action is passed along to an
aggregation node for analysis and action. In the Smart Grid example,
each substation might have its own aggregation node that reports the
operational status of each downstream feeder and lateral.
 ● Data that is less time sensitive is sent to the cloud for historical
analysis, big data analytics, and long-term storage (see sidebar). For
example, each of thousands or hundreds of thousands of fog nodes
might send periodic summaries of grid data to the cloud for historical
analysis and storage.
 Benefits of Fog Computing

 Extending the cloud closer to the things that generate and act
on data benefits the business in the following ways:
 ● Greater business agility: With the right tools, developers
can quickly develop fog applications and deploy them where
needed. Fog applications program the machine to operate in
the way each customer needs.
 ● Better security: Protect your fog nodes using the same
policy, controls, and procedures you use in other parts of your
IT environment. Use the same physical security and
cybersecurity solutions.
 Benefits of Fog Computing

 ● Deeper insights, with privacy control:

Analyze sensitive data locally instead of sending it
to the cloud for analysis. Your IT team can monitor
and control the devices that collect, analyze, and
store data.
 ● Lower operating expense: Conserve network
bandwidth by processing selected data locally
instead of sending it to the cloud for analysis.
 Conclusion on Fog Computing

 Fog computing gives the cloud a companion to handle the

two exabytes of data generated daily from the Internet of
Things. Processing data closer to where it is produced and
needed solves the challenges of exploding data volume,
variety, and velocity. Fog computing accelerates awareness
and response to events by eliminating a round trip to the
cloud for analysis. It avoids the need for costly bandwidth
additions by offloading gigabytes of network traffic from
the core network. It also protects sensitive IoT data by
analyzing it inside company walls.