Project I - Narrative: The goal of Project I is to develop a server process that...

Transcribed Image Text:

Project I - Narrative: The goal of Project I is to develop a server process that communicates with multiple clients using sockets. The programs should be console-mode application (text-base, old MS-DOS type application) that should run on Win32 environment. The server process is supposed to be started at one of the PCs (Windows-based IBM-compatible) before any client makes a connection request to it. Client processes should be started at different PCs (for testing purpose, you can run clients and a server on the same host, but a server and clients should be able to communicate between different network hosts). The source code for client process will be provided by the instructor (Fujinoki). The client process is designed to take three parameters at the command prompt when one is started. The format of the three parameters at the command prompt is: client <CLIENT ID#> <SERVER IP ADDREES> <SERVER PORT #> Client ID: The client ID is the identification of clients that uniquely identify each of the multiple clients a server will deal with. The client ID is simply an integer (e.g., 1, 2, ...) assigned to each client that talks to the same server (therefore the same client ID can not be assigned to more than one client). Server IP address: The IP address of a server this client is going to talk to. Server Port Number: A server is listening to a particular TCP port at a network host with an IP address. In order for a client to talk to a server, both IP address and YCP port number must be specified. What this client and server application will perform: After a client process is started by entering the command shown above, the client sends a connection request (using "connect" at the client) to the server process at a specified network host computer. Then, a TCP/IP connection will be established between the server and the client. At the server side, each time the server receives a connection request from a client, the server process should display a message, "a connection request arrived!" on its local display. Then, the server process extracts the client's IP address and the TCP port number. After a socket connection is successfully established, the client process should send its client ID. The server process has a specific client called "prohibited client". The client should send its client ID to the server and the server should receive the message (i.e., the client ID) through the socket connection and display the following message, "Request from client #", where # is the ID of the client. After the server process displays the client ID, the server returns the timestamp (the timestamp at the arrival of the second message) to the requesting client if the client is not the prohibited client. If it is the prohibited client, the server returns a message for rejection ("Your access is denied by this server!") to the client, instead of the timestamp message. The server process, then, should wait for one second after it returns the timestamp to the client. The client should receive the message from the server (either timestamp or rejection message) and display it on the client's local display. After the client displays the message, the client should disconnect the socket connection and start the whole process from the beginning. Multiple clients (but up to three in this project) should be able to connect to the server at the same time (and the server 1 should be able to handle up to three clients simultaneously). Each client should be designed to repeat this procedure 15 times and after 15 repeats, it should terminate itself. For each repeat, the client process will wait about one second. In the server side, execution should go back to "accept" function call. Technical Requirements: a. Your source code file should be developed using MS Visual C++ (in Visual Studio) for IBM-compatible PCs. Due to the large class enrolment, program source code files written in any other programming language, for any other compilers, or for any other hardware platforms, will not be accepted for grading. b. c. Your server must communicate with the client (client.cpp) posted to the CS447 home and the client process can not be modified. Declaration of the prohibited client: the IP address of the prohibited client must be declared using #define declarative at the beginning of your source code file. d. The messages displayed by the client process should not contain any extra contents. e. Your server process must be ready for serving multiple clients at any time (even when a client completes, your server must be up and running, ready for other clients). (2) Connection type: connection-oriented socket (stream socket = TCP) Required Process Structure: Display: "a request arrived".. Display: "From client X" SERVER Socket Bind Listen Accept Read Write Wait 1 sec. CLIENT Socket Connect Write Read Close Wait 1 sec. End 3 clients Repeat 5 times Display: "Time: XX:XX" Project I - Narrative: The goal of Project I is to develop a server process that communicates with multiple clients using sockets. The programs should be console-mode application (text-base, old MS-DOS type application) that should run on Win32 environment. The server process is supposed to be started at one of the PCs (Windows-based IBM-compatible) before any client makes a connection request to it. Client processes should be started at different PCs (for testing purpose, you can run clients and a server on the same host, but a server and clients should be able to communicate between different network hosts). The source code for client process will be provided by the instructor (Fujinoki). The client process is designed to take three parameters at the command prompt when one is started. The format of the three parameters at the command prompt is: client <CLIENT ID#> <SERVER IP ADDREES> <SERVER PORT #> Client ID: The client ID is the identification of clients that uniquely identify each of the multiple clients a server will deal with. The client ID is simply an integer (e.g., 1, 2, ...) assigned to each client that talks to the same server (therefore the same client ID can not be assigned to more than one client). Server IP address: The IP address of a server this client is going to talk to. Server Port Number: A server is listening to a particular TCP port at a network host with an IP address. In order for a client to talk to a server, both IP address and YCP port number must be specified. What this client and server application will perform: After a client process is started by entering the command shown above, the client sends a connection request (using "connect" at the client) to the server process at a specified network host computer. Then, a TCP/IP connection will be established between the server and the client. At the server side, each time the server receives a connection request from a client, the server process should display a message, "a connection request arrived!" on its local display. Then, the server process extracts the client's IP address and the TCP port number. After a socket connection is successfully established, the client process should send its client ID. The server process has a specific client called "prohibited client". The client should send its client ID to the server and the server should receive the message (i.e., the client ID) through the socket connection and display the following message, "Request from client #", where # is the ID of the client. After the server process displays the client ID, the server returns the timestamp (the timestamp at the arrival of the second message) to the requesting client if the client is not the prohibited client. If it is the prohibited client, the server returns a message for rejection ("Your access is denied by this server!") to the client, instead of the timestamp message. The server process, then, should wait for one second after it returns the timestamp to the client. The client should receive the message from the server (either timestamp or rejection message) and display it on the client's local display. After the client displays the message, the client should disconnect the socket connection and start the whole process from the beginning. Multiple clients (but up to three in this project) should be able to connect to the server at the same time (and the server 1 should be able to handle up to three clients simultaneously). Each client should be designed to repeat this procedure 15 times and after 15 repeats, it should terminate itself. For each repeat, the client process will wait about one second. In the server side, execution should go back to "accept" function call. Technical Requirements: a. Your source code file should be developed using MS Visual C++ (in Visual Studio) for IBM-compatible PCs. Due to the large class enrolment, program source code files written in any other programming language, for any other compilers, or for any other hardware platforms, will not be accepted for grading. b. c. Your server must communicate with the client (client.cpp) posted to the CS447 home and the client process can not be modified. Declaration of the prohibited client: the IP address of the prohibited client must be declared using #define declarative at the beginning of your source code file. d. The messages displayed by the client process should not contain any extra contents. e. Your server process must be ready for serving multiple clients at any time (even when a client completes, your server must be up and running, ready for other clients). (2) Connection type: connection-oriented socket (stream socket = TCP) Required Process Structure: Display: "a request arrived".. Display: "From client X" SERVER Socket Bind Listen Accept Read Write Wait 1 sec. CLIENT Socket Connect Write Read Close Wait 1 sec. End 3 clients Repeat 5 times Display: "Time: XX:XX"

Answer rating: 100% (QA)

Answer serverc include include include include include include include void errorconst char msg perrormsg exit1 int mainint argc char argv int sockfd newsockfd portno socklent clilen char buffer256 st... View the full answer