Scribd
Upload
5 views6 pages

Internet

The document discusses how browsers function as rendering engines by requesting web resources from servers and displaying them. It describes the main components of browsers including the rendering engine, which can display HTML, XML, images and other file types using plugins. It also outlines the main flow of how rendering engines obtain and display requested document contents.

Uploaded by

Amrit Sapkota
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
5 views6 pages

Internet

The document discusses how browsers function as rendering engines by requesting web resources from servers and displaying them. It describes the main components of browsers including the rendering engine, which can display HTML, XML, images and other file types using plugins. It also outlines the main flow of how rendering engines obtain and display requested document contents.

Uploaded by

Amrit Sapkota
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Browser as a rendering engine:

Text, HTML, gif, and jpeg


• The main function of a browser is to present the web resource we choose,
by requesting it from the server and displaying it in the browser window.
• The resource is usually an HTML document, but may also be a PDF, image,
or some other type of content.
• The location of the resource is specified by the user using a URI (Uniorm
Resource Identifier).
• The way the browser interprets and displays HTML files is specified in the
HTML and CSS specifications. These specifications are maintained by the
W3C (World Wide Web Consortium) organization

1
Browser as a rendering engine:
Text, HTML, gif, and jpeg
Main components of browsers:

2
Browser as a rendering engine:
Text, HTML, gif, and jpeg
Rendering Engine:
• Rendering, that is display of the requested contents on the browser screen.
• By default the rendering engine can display HTML and XML documents and
images. It can display other types of data via plug-ins or extension; for
example, displaying PDF documents using a PDF viewer plug-in
• Different browsers use different rendering engines: Internet Explorer uses
Trident, Firefox uses Gecko, Safari uses WebKit. Chrome and Opera (from
version 15) use Blink, a fork of WebKit.
• WebKit is an open source rendering engine which started as an engine for
the Linux platform and was modified by Apple to support Mac and Windows
3
Browser as a rendering engine:
Text, HTML, gif, and jpeg
The main Flow
• The rendering engine will start getting the contents of the requested
document from the networking layer. This will usually be done in 8kB
chunks

4
Browser as a rendering engine:
Text, HTML, gif, and jpeg

Fig: Webkit main Flow 5


References
• RFC-2616: http://www.w3.org/Protocols/rfc2616/rfc2616.html
• TCP GUIDE:
http://www.tcpipguide.com/free/t_TCPIPHypertextTransferProto
colHTTP.htm
• IBM Software Information Center - The HTTP protocol
http://publib.boulder.ibm.com/infocenter/cicsts/v3r1/topic/com.
ibm.cics.ts31.doc/dfhtl/topics/dfhtl29.htm

You might also like