ECE536 Computer Software Systems

Assignment #3 (7%)

Spring 2005, handout #536006
Parts 1 & 2 due: Thursday, 02/24/05
Parts 3 & 4 due: Tuesday, 03/08/05

Objectives

• To use RPC to implement client-server paradigms

Submittal

• A cover page to show your name, student number, 536number. Your source files and your test run.

Assignment

With SUN RPC, implement a RESTAURANTCLUB client/server pair to provide restaurant lookup/exchange services.

Part 1 (10%):

1. Establish your own restaurant guide by entering three favorite restaurants (no more, no less, so we can make sure the largest collection will not be greater than 45). A restaurant record should have the following information:
   • RestId, int, // unique in the class
   • RestTitle, char[100], // restaurant title
   • RestCateg, char[100], // Category, such as Chinese,Italian
   • RestAddr, char[100], // restaurant street address
   • RestClubIP, char[100], // where this record is retrieved from
   • RestClubStamp, char[100], // timestamp this record is retrieved
   • RestClubIdPath, int[15], // which server this record is retrieved from
   • RestAccessNum, int, // how many times this restaurant info has been requested
   Everyone in the class is assigned a RestClubId, 536xx at your WebCt record. Then, your own RestIds should be 536xx01, 536xx02, and 536xx03. For the three restaurant records you created/own, RestAccessNum is initially zero, RestClubStamp is the date/time your restaurant collection is created, RestClubIdPath's first entry is your own RestClubId, and RestClubIP is NULL. To make your collection persistent, your need to write them on disk.

   Part 2 (40%):

2. Write the server part of the restaurant club to service restaurant info requests via RPC calls, where the interface definition is,

       program RESTAURANTCLUB {
         version RTCLUB1ST {
            unsigned int getRestNum (unsigned int RestClubId) = 1;
            RestList getRestList (unsigned int RestClubId) = 2;
            RestInfo getRestRecord (unsigned int RestId) = 3;
            } = 1;
         } = 536xx;
   

   • getRestNum, bringing RestClubId that makes the request, will return the number of restaurant records in your current restaurant collection.
   • getRestList will return the entire list of restaurants titles and IDs.
   • getRestRecord will return the requested restaurant record, which is specified by its ID.
   Here, you need to follow the definition of RestInfo and RestList as follows:

       struct RestInfo {
         int  RestId;
         char RestTitle[100];
         char RestCateg[100];
         char RestAddr[100];
         int  RestClubIdPath[15];
         };
       struct RestList {
         char RestTitle[100];
         int  RestId;
         struct RestList *NextRest;
         };
   

   Also, in your own format, log all requests with a timestamp.

3. Write the client part of the restaurant club to make restaurant info requests via RPC calls. Your client program needs to dynamically input two arguments: ServerName and RestClubId (which is actually the program number) to identify a server. Your can design your own user interface. Every time you make a restaurant request, you can decide if you want to update your own restaurant collection with the requested restaurant. If the update is carried out,
   • Make sure you do not have any duplicated entry in your collection.
   • Fill out RestClubIP and RestClubStamp.
   • Append your own RestClubId to RestClubIdPath.

4. Turn in your source code for both programs.

5. Run your server and client pair and turn in your testrun.

   Part 3 (25%):

6. Pick one Solaris machine to run your server program. Advertise your selected machine name, IP address, and your RestClubId at your class web page@WebCT to attract other peers' interests.

   Run your server program continuously between 02/24/05 and 03/07/05. To run it as a daemon process, you can utilize 'nohup'. However, after 03/07/05, you have to cleanup (kill -9 procID) your process. In order to find out the daemon process's proc ID, you can use:

     ps -elf | grep yourProgName
     ps -auxw | grep yourProgName
   

7. Turn in your server log and report:
   • the number of accesses are made.
   • list of RestClubIds who made at least one request.
   You need to have at least five distinct RestClubIds to appear in your server log.

   Part 4 (25%):

8. Look for interesting restclub servers to make queries during the open week. You can check the web pages to get server names and RestClubIds. You can also use

       rpcinfo -p | grep 536
   

   to see which servers are available.

9. You need to update your restaurant collection during queries so that at the end of open week your restaurant collection will contain restaurant records from at least five distinct RestClubIds besides your own three restaurants.

10. Turn in the complete information of your final collection.
11. For RPC, here are several links that may help:
    Examples: http://www.cs.rpi.edu/~hollingd/netprog99/rpc/
    Tutorial: http://www.cs.cf.ac.uk/Dave/C/node33.html
    The SUN RPC document is posted in the course content page, under module #2.

Assigned by Dr. Shu, shu@ece.unm.edu