








Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
This lecture was delivered by Prof. Arun Ullal at Ankit Institute of Technology and Science for Web Programming course. It includes: Course, Overview, Protocols, World, Wide, Web, HTML, JavaScript, Perl, PHP
Typology: Slides
1 / 14
This page cannot be seen from the preview
Don't miss anything!









understand the technology and protocols underlying the World Wide Web
become familiar with common tools and techniques for developing Web-based applications, both client-side and server-side
develop a working knowledge of HTML, JavaScript, Perl and PHP as languages for developing Web applications
Joseph Licklider at M.I.T. (a “time-sharing network of computers”) Paul Baran at Rand (tasked with designing a “survivable” communications system that could maintain communication between end points even after damage from a nuclear attack) Donald Davies at National Physics Laboratory in U.K.
survivability (i.e., network still functions despite a local attack) fault-tolerance (i.e., network still functions despite local failure)
contrast with phone system, electrical system which are highly centralized services
connected computers at UC Los Angeles, UC Santa Barbara, Stanford Research Institute, and University of Utah allowed researchers to share data, communicate 56Kb/sec communications lines (vs. 110 b/sec over phone lines)
e-mail introduced in 1972 decentralization made adding new computers easy TCP/IP developed in the mid 1970s for more efficient packet routing migration of ARPANET to TCP/IP completed 1 January, 1983 ~1000 military & academic host computers connected by 1984
created NSFNET for academic research in 1986 ARPANET was retained for military & government computers
businesses and individuals also connecting as computing costs fell ~1,000,000 computers by 1992
Internet Society: Internet Engineering Task Force Internet Architecture Board Internet Assigned Number Authority World-Wide-Web Consortium (W3C)
...
online hypertext systems began to be developed in 1960's e.g., Ted Nelson and Andy van Dam's Hypertext Editing System (HES), Doug Englebert's NLS (oN-Line System) in 1987, Apple introduced HyperCard (a hypermedia system that predated the WWW)
designed a (Non-WYSIWYG) language for specifying document content
the intuitive, clickable interface helped make hypertext accessible to the masses made the integration of multimedia (images, video, sound, …) much easier Andreessen left NCSA to found Netscape in 1994 cheap/free browser further popularized the Web (75% market share in 1996)
contents (text/links/images) are the same each time it is accessed
e.g., online documents, most homepages
HyperText Markup Language (HTML) is used to specify text/image format
pages can be fluid, changeable (e.g., rotating banners) must be able to react to the user's actions, request and process info, tailor services
e.g., amazon.com
programs can be written to conform to the CGI when a Web page submits, data from the page is sent as input to the CGI program CGI program executes on server, sends its results back to browser as a Web page
good if computation is large/complex or requires access to private data see http://hoohoo.ncsa.uiuc.edu/cgi/ we will discuss CGI programming using Perl, but other languages possible as well (such as Python, Ruby, etc.)
some of these are vendor-specific alternatives to CGI (such as Microsoft’s ASP) provide many of the same capabilities as CGI programs but using HTML-like tags some of these technologies might require functionality to be enabled in the client’s browser (e.g. Ajax generally requires the use of Javascript combined with PHP or some other server- based programming component)
more complex, requires server privileges, but can still be (mostly) secure
static components?
dynamic components? client-side? JavaScript? Java applet? server-side? CGI? ASP?
gmail (uses Ajax for lots of its dynamic functions)