1. Sports scores. There is a table in the middle of your page, www.sportserver.com, with up-to-date sports scores. You have a special database server db.sportserver.com, is running a program that keeps a database updated minute by minute with these scores.
   
   Answer: On the Client Side there is a table on the webpage which contains a javascript that allows the user to request information, in this case the most recent sports scores. The user points to a URL or reference tag (which is hidden from the user) and initiates a request for the scores that reside on the Server Side The script sends the request to the database server (db.sportserver.com) which is running a program that constantly updates the scores by accessing available information in a database. The information (scores) is sent back to the user on the Client Side through the browser. Both Server-and Client sides are best for this application.
2. Webcam. A program located on a dedicated computer is taking snapshots of my pet canary from a video camera every 30 seconds, and uploading them via FTP to a file called "mycanary.jpg" on the web server. My web page, www.mycanarycam.com, is supposed to redisplay the current contents of "mycanary.jpg" at least every 30 seconds.
   
   Answer: On the Sever Side there is a script implementing a command to access the video camera output every 30 seconds. The script constantly replaces the file by over writing it. This would be a continuos loop. The file would be imported, saved and overwritten, every 30 seconds by retaining the original file name "mycanary.jpg". The file would then be uploaded via FTP using the same name (mycanary.jpg) to the web server. Once on the web server (Server Side) the file replaces the file created 30 seconds ago with the new 30 second file. The file can now be seen or accessed by users who have access to the a webpage or website on Client Side sharing the database that resides on the Server Side. Server-Side the best usage for this. In fact it seems to be the only logical solution..
3. Movietickets.com. A movie theater implements a simple movie ticket reservation system. You fill out the form including your charge card, press the button, and an e-mail is sent to the theater. The order is processed manually and the tickets are waiting for you when you get there.
   
   Answer: The user accesses the Movietickets.com web page (Client Side) which contains a form that requests his/her charge card number, name,.what move is playing, what time etc. The form is connected to the Movertickets server (server side), the user can access the database for answers: when the movies are playing, what time the movies are playing, what the theater location is, what dates the movies are playing and what cost are the tickets. The user submits the information by pressing a button and sends an e-mail to the Theaters Mail Server (Server Side). An employee at the theater opens the e-mail and processes the information. The employee responds by sending back an e-mail to the user’s mail server (Server Side) letting the user know that the request has been received and that the tickets can be picked up at the box office. Client-Side is the best usage of MovieTicket.com, but you still need the server to process the information.

Describe whether you would do it on the client or the server. Which is the better usage.

Rita Webster CA274 22547 Administering a Web Site.