Difference: CS290Spring09Hw (19 vs. 20)

Revision 202009-03-30 - KonstantinosMenychtas

Line: 1 to 1
 
META TOPICPARENT name="CS290Spring09"

CSC 290A, Spring 2009: Homework

Line: 14 to 14
 

Team Project: Instant Messaging Sever for Browser Clients. NEW

Deleted:
<
<

Stage 1: Basic server

 In this project, you will work in a group to develop an instant-messaging server. The basic server accepts HTTP requests to establish client accounts and passwords, maintain on-line status, organize pairwise and group communication, and store message history.

The client can be any Internet browser program such as Firefox or IE. Let's say that an interested user learned about your server and its URL through you, a link on some web page, or your advertisement on campus. The functionalities of the server are organized in several basic page views. First, the user comes to the front page of the server, which allows a new user to register and an existing user to log in. You may use clear text to transfer and store user passwords, but we strongly recommend you use the encryption support of HTTP.

Line: 34 to 32
  The project is evaluated at the weekly report for 15 min per team each Tuesday during class. The report has two parts. The first is a slide presentation of the progress in the last week and the plan for the next week. It includes progress made not just in system implementation but equally importantly system design and user demand/feedback analysis. You will use the software development process known as agile development---chiefly rapid prototyping and iterative improvements. The second part of the report is your system, or if the system is not yet developed, a demonstration of some features of your design.
Changed:
<
<
The length of stage 1 is about three weeks starting from Friday March 27 and ending April 14, with three in-class presentations on March 31, April 7, and April 14.

Stage 2: Extensible server

>
>
The length of this first stage is about three weeks starting from Friday March 31 and ending April 21, with three in-class presentations on April 7, April 14 and April 21.
 
Changed:
<
<
Depending on the available time and the progress and discussion of stage 1, we will extend the design of the basic server to allow a user to add and distribute new functionalities. We will post the design requirements in the next week.
>
>
Extensions:
 
Changed:
<
<
For resources, see class slides and references especially on the following subjects:
>
>
Depending on the available time and the progress and discussion of first stage, we will extend the design of the basic server to allow a user to add and distribute new functionalities.The design requirements will be updated according to progress, but some references with ideas on possible extensions can be found below:
 
  • HTTP/CGI/Web 2.0 programming, class schedule table Feb. 19, 23, and 25.
  • Source-code control through subversion, class schedule table Feb. 12.
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding URCS? Send feedback