Please submit your code ONLY by using my upload
utility, onto "UPLOAD FINAL ASSIGNMENT" area.
FOLLOW THE NAMING CONVENTION.
PLEASE READ THE ENTIRE ASSIGNMENT (THIS PAGE) VERY CAREFULLY.
UPDATES TO THIS ASSIGNMENT WILL POSTED ON "MESSAGE
OF THE DAY" PAGE.
ADDITIONAL DESCRIPTION:
This assignment is a continuation to the first two assignments except
the following parts:
SERVER:
The second file is called server.list which contains a list of systems
where other LDAP servers are running on.
Here is the format of the file:
afs20.njit.edu
afs23.njit.edu
afs33.njit.edu
IP address is also acceptable. You may add additional information such
as port number, etc.. in that file.
Once the server is invoked, it will read the data file ".in" then the
server list file "server.list" each server will try to synchronize its
data it reads from ".in" file, with other servers; if a server is down,
it will just try to connect to the next in the list, after end of the list
it should try from the top. Time out should be short e.g. 2 - 5 seconds.
CLIENT:
The client should also read the same server.list file which servers
do and try to connect to a server. If the first server is down or went
down, it should try to connect to the next one in the list. Client(s) will
run in the foreground since they require user input.
NOTE:
There is no assumption made as to what mechanism will be used
to implement this system. The description given above states the problem
in an abstract way to allow different approaches to be used with the same
result and functionality. Your .des file must be fully compliant with my
specifications and state all the BUGS: and any special instructions which
your program requires to run.
SUBMIT:
Submit two files only:
A TAR file containing all the programs you wrote and the description
".des" file.
The .des file MUST be outside of the tar file.
Please direct questions or errors to: CIS604@cis.njit.edu