CS 490W World Wide Web Networking
Spring 1998

    Time and Place:      TTh 4:30--5:45 PM, UNIV 317.
    Professor:           David K. Yau, CS 132, yau@cs.purdue.edu.
    Office hours:        TTh 3:30--4:30 PM

    Teaching assistant:  Jing Jia, jiaj@cs.purdue.edu.
    Office hours:        M 3:20--4:20 PM, W 3:00--4:00 PM

Prerequisites

Synopsis

We will study enabling technologies and common applications (particularly distributed multimedia) for the World Wide Web. Emphasis will be placed on networking aspects (such as LAN, WAN, TCP/IP, UDP, HTTP, mbone multicast) of the subject. Significant programming in Java and Perl (to a lesser extent) will be required for homeworks and the course project.

Syllabus

  1. Object-oriented programming review
  2. World Wide Web overview
  3. Middleware
  4. Common Gateway Interface/Perl
  5. Java
  6. Java topics
  7. Local area networks
  8. Internet/Wide-area networks
  9. TCP/IP
  10. Network programming (client/server, RPC, Corba)
  11. Multimedia technologies
  12. Compression and multimedia standards
  13. Multimedia communication
  14. Mbone and multicasting
  15. Selected topics: electronic commerce, security, ...
Syllabus handout (postscript)

Textbooks

Required:
  1. Amjad Umar, Object-oriented Client/Server Internet Environments, Prentice-Hall ISBN 0-13-375544-4
  2. Arnold/Gosling, Java Programming Language, 2/e, Addison-Wesley
  3. Shishir Gundavaram, CGI Programming on the World Wide Web, O'Reilly ISBN 1-5659
Recommended:
  1. Douglas Comer, Internetworking with TCP/IP, Vol 1, 3e, Prentice-Hall
  2. Raghavan/Tripathi, Networked Multimedia Systems, Prentice-Hall

Grading

Lectures

1. Overview
2. OOP Review
3. World Wide Web Overview
4. Common Gateway Interface
5. CGI/Perl (Gundavaram) 
   - Input to CGI programs
   - Output from CGI programs
   - Server side includes
   - Forms
   - Dynamic and animated output
   - Multiple form interactions (hidden fields, CGI includes, Netscape cookies)
   - CGI gateways (with postscript, gnuplot, Unix manpage, relational databases, ...)
6. Java 
   - Interfaces
   - Exceptions
   - Threads
   - Network programming
   - Abstract Window Toolkit
   - Applets
7. Multimedia systems and media compression

Final

Final exam will be on Thurs 5/7, 7:00--9:00 pm, WTHR 320. Closed book, closed notes. A syllabus and review is available for your reference.

You can look at the actual final exam used.

Midterm

Midterm will be on 3/17, 4:30--5:45 pm (class time). Closed book, closed notes. You will be tested on materials covered up to the review session on 3/5 (class time). 
Place:
   UNIV 317   last name beginning with letter A--O
   UNIV 301   last name beginning with letter P--Z

Homeworks

1. Homework #1 (Given 2/3/98; due 2/10/98)
(Sample solutions now in the Math Library!)
2. Homework #2 (Given 2/26/98; due 3/5/98)
3. Homework #3 (Given 4/9/98; due 4/16/98)
4. Homework #4 (Given 4/23/98; due 4/30/98)

Sound files (To download: hold down Shift key, and press the left mouse button, with the mouse pointer on a link): laugher.au, whistle.au, train.au

Term Project

This is a group project. Five students per group -- if you have not sent us your proposed grouping, please do so (send email to your TA jiaj@cs.purdue.edu) as soon as possible. There are handouts for two projects here. Please read the descriptions, and propose to us the one that you would like to work on. (Project due date: 4/30/98.)

1. Internet Board Games
2. Online Registration System

Assignment policy

  1. Homeworks are due at the beginning of class on their due day. No late homeworks will be accepted.
  2. Students are encouraged to discuss concepts required to complete a homework. However, write-up on solutions and coding (including the coding of data structures) for programming questions must be individual efforts.
  3. Students collaborating (e.g. coding up a solution together) on a homework must explicitly state so, in which case they will receive equal share of the credit.
  4. Students (1) collaborating without acknowledgement, or (2) taking the work of someone else and submitting it as their own (with or without changes), receive zero for the homework and will be reported to the Dean of Students.
  5. Students are not expected to copy solutions from published work (in books other than our listed textbooks, journals, conference proceedings, etc), and if they make use of published results in their solutions, must give proper reference to the original source(s).
  6. Students must actively prevent their work from being plagiarized. This includes setting proper access protection for program files.
Adapted from guidelines given by Professor Schulzrinne of Columbia.