程序代写代做代考 information theory database c/c++ AWS compiler EE450 Socket Programming Project, Fall 2018

After querying backend-
server C:

“The AWS sent link ID=, size=, power=, and
link information to Backend-Server C using UDP over port ”

After receiving result from
backend-server C:

“The AWS received outputs from Backend-Server C using UDP over port ”

After sending the result to
the client:

“The AWS sent delay=ms to the client using TCP over port ”

After sending the final
result to the monitor:

“The AWS sent detailed results to the monitor using TCP over port ”

After sending result to
monitor and client If no result

is returned by server A, B:

“The AWS sent No Match to the monitor and the client using TCP over ports and , respectively”

ON SCREEN MESSAGES:
Table 8. Client on screen messages

Event On Screen Message (inside quotes)

Booting Up: “The client is up and running”

Upon sending the input to
AWS:

“The client sent ID=, size=, and
power= to AWS”

After receiving the result from
AWS:

“The delay for link is ms”

If no matches are found for the
link:

“Found no matches for link ”

Example Output to Illustrate Output Formatting:
Please note that the number in the example output is for display only, not a real result.

Backend-Server A Terminal:
The Server A is up and running using UDP on port <21319>.
The Server A received input <3>
The Server A has found < 1 > matches
The Server A finished sending the output to AWS

Backend-Server B Terminal:
The Server B is up and running using UDP on port <22319>
The Server B received input <3>
The Server B has found < 0 > matches
The Server B finished sending the output to AWS

Backend-Server C Terminal:
The Server C is up and running using UDP on port <23319>
The Server C received link information of link <3>, file size <10000>, and signal power <10>
The Server C finished the calculation for link <3>
The Server C finished sending the output to AWS

ON SCREEN MESSAGES:
Table 9. Monitor on screen messages

Event On Screen Message (inside quotes)

Booting Up: “The monitor is up and running.”

After receiving the input from
AWS:

“The monitor received link ID=, size=,
and power= from the AWS”

After receiving the result from
AWS:

“The result for link :
Tt = ms,
Tp = ms,

Delay = ms”

If no matches are found for the
link:

“Found no matches for link ”

AWS Terminal:
The AWS is up and running
The AWS received link ID=<3>, size=<10000>, and power=<10> from the client using
TCP over port <25319>
The AWS sent link ID=<3>, size=<10000>, and power=<10> to the monitor using TCP
over port <26319>
The AWS sent link ID=<3> to Backend-Server A using UDP over port < 24319 >
The AWS sent link ID=<3> to Backend-Server B using UDP over port < 28319 >
The AWS received < 1 > matches from Backend-Server < A > using UDP over port < 24319 >
The AWS received < 0 > matches from Backend-Server < B > using UDP over port < 28319 >
The AWS sent link ID=<3>, size=<10000>, power=<10>, and link information to
Backend-Server C using UDP over port < 27319 >
The AWS received outputs from Backend-Server C using UDP over port < 27319 >
The AWS sent delay=<10>ms to the client using TCP over port < 25319 >
The AWS sent detailed results to the monitor using TCP over port <26319>
The AWS sent No Match to the monitor and the client using TCP over ports <25319> and
<26319>, respectively

Client Terminal:
The client is up and running
The client sent link ID=<3>, size=<10000>, and power=<10> to AWS
The delay for link <3> is <10>ms
Found no matches for link <4>

Monitor Terminal:
The monitor is up and running
The monitor received input=<3>, size=<10000>, and power=<10> from the AWS
The result for link <3>:
Tt = <3>ms
Tp = <7>ms
Delay = <10>ms
Found no matches for link <4>

Assumptions:

1. You have to start the processes in this order: backend-server (A), backend-
server (B), backend-server (C), AWS (D), Client, Monitor.

2. If you need to have more code files than the ones that are mentioned here, please

use meaningful names and all small letters and mention them all in your README
file.

3. You are allowed to use blocks of code from Beej’s socket programming tutorial

(Beej’s guide to network programming) in your project. However, you need to mark
the copied part in your code.

4. When you run your code, if you get the message “port already in use” or “address

already in use”, please first check to see if you have a zombie process (see
following). If you do not have such zombie processes or if you still get this message
after terminating all zombie processes, try changing the static UDP or TCP port
number corresponding to this error message (all port numbers below 1024 are
reserved and must not be used). If you have to change the port number, please do
mention it in your README file and provide reasons for it.

5. You may create zombie processes while testing your codes, please make sure

you kill them every time you want to run your code. To see a list of all zombie
processes, try this command: >>ps –aux | grep ee450
Identify the zombie processes and their process number and kill them by typing at the
command-line: >>kill -9 processnumber

Requirements:

1. Do not hardcode the TCP or UDP port numbers that are to be obtained dynamically.

Refer to Table 3 to see which ports are statically defined and which ones are
dynamically assigned. Use getsockname() function to retrieve the locally-bound
port number wherever ports are assigned dynamically as shown below:
/*Retrieve the locally-bound name of the specified socket and
store it in the sockaddr structure*/
Getsock_check=getsockname(TCP_Connect_Sock,(struct sockaddr
*)&my_addr, (socklen_t *)&addrlen);

//Error checking
if (getsock_check== -1)

{ perror(“getsockname”);
exit(1);

}

2. The host name must be hardcoded as localhost (127.0.0.1) in all codes.

3. Your client should terminate itself after all done. And the client can run multiple times to
send requests. However, the backend servers and the AWS should keep running and be
waiting for another request until the TAs terminate them by Ctrl+C. It they terminate
before that, you will lose some points for it.

4. All the naming conventions and the on-screen messages must conform to the

previously mentioned rules.

5. You are not allowed to pass any parameter or value or string or character as a
command-line argument except while running the client in Phase 1.

6. All the on-screen messages must conform exactly to the project description. You

should not add anymore on-screen messages. If you need to do so for the
debugging purposes, you must comment out all of the extra messages before you
submit your project.

7. Please do remember to close the socket and tear down the connection once you

are done using that socket.

Programming platform and environment:

1. All your submitted code MUST work well on the provided virtual machine Ubuntu.

2. All submissions will only be graded on the provided Ubuntu. TAs won’t make any
updates or changes to the virtual machine. It’s your responsibility to make sure
your code working well on the provided Ubuntu. “It works well on my machine” is
not an excuse and we don’t care.

3. Your submission MUST have a Makefile. Please follow the requirements in the

following “Submission Rules” section.

Programming languages and compilers:

You must use only C/C++ on UNIX as well as UNIX Socket programming commands and
functions. Here are the pointers for Beej’s Guide to C Programming and Network
Programming (socket programming):

http://www.beej.us/guide/bgnet/

(If you are new to socket programming please do study this tutorial carefully as soon as
possible and before starting the project)

http://www.beej.us/guide/bgc/

You can use a unix text editor like emacs to type your code and then use compilers such
as g++ (for C++) and gcc (for C) that are already installed on Ubuntu to compile your
code. You must use the following commands and switches to compile yourfile.c or
yourfile.cpp. It will make an executable by the name of “yourfileoutput”.

gcc -o yourfileoutput yourfile.c
g++ -o yourfileoutput yourfile.cpp

Do NOT forget the mandatory naming conventions mentioned before!

Also inside your code you need to include these header files in addition to any other
header file you think you may need:

#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include

http://www.beej.us/guide/bgnet/
http://www.beej.us/guide/bgc/

Submission Rules:

1. Along with your code files, include a README file and a Makefile. In the
README file write
a. Your Full Name as given in the class list
b. Your Student ID
c. What you have done in the assignment.
d. What your code files are and what each one of them does. (Please do not

repeat the project description, just name your code files and briefly mention
what they do).

e. The format of all the messages exchanged.
g. Any idiosyncrasy of your project. It should say under what conditions the project

fails, if any.
h. Reused Code: Did you use code from anywhere for your project? If not, say so.

If so, say what functions and where they’re from. (Also identify this with a
comment in the source code.)

Submissions WITHOUT README AND Makefile
WILL BE SUBJECT TO A SERIOUS PENALTY

Makefile tutorial:
https://www.cs.swarthmore.edu/~newhall/unixhelp/howto_makefiles.html

About the Makefile: makefile should support following functions:

make all Compiles all your files and
creates executables

make serverA Runs server A

make serverB Runs server B

make serverC Runs server C

make aws Runs AWS

make monitor Runs monitor

./client Starts the client

https://www.cs.swarthmore.edu/%7Enewhall/unixhelp/howto_makefiles.html

TAs will first compile all codes using make all. They will then open 6 different
terminal windows. On 5 terminals they will start servers A, B, C and AWS using
commands make serverA, make serverB, make serverC, make aws and make
monitor. Remember that servers and monitor should always be on once
started. Client can connect again and again with different input values and function.
On the sixth terminal they will start the client as “./client
”. TAs will check the outputs for multiple values of input. The terminals
should display the messages shown in table 4, 5, 6, 7 and 8.

2. Compress all your files including the README file into a single “tar ball” and call

it: ee450_yourUSCusername_session#.tar.gz (all small letters) e.g. my filename
would be ee450_nanantha_session1.tar.gz. Please make sure that your name
matches the one in the class list. Here are the instructions:

a. On your VM, go to the directory which has all your project files. Remove all
executable and other unnecessary files. Only include the required source code
files, Makefile and the README file. Now run the following commands:

b.
>> tar cvf ee450_yourUSCusername_session#.tar *
>> gzip ee450_yourUSCusername_session#.tar

Now, you will find a file named “ee450_yourUSCusername_session#.tar.gz” in
the same directory. Please notice there is a star(*) at the end of first command.
Any compressed format other than .tar.gz will NOT be graded!

3. Upload “ee450_yourUSCusername_session#.tar.gz” to the Digital Dropbox on the

DEN website (DEN -> EE450 -> My Tools -> Assignments -> Socket Project). After
the file is uploaded to the dropbox, you must click on the “send” button to actually
submit it. If you do not click on “send”, the file will not be submitted.

4. D2L will and keep a history of all your submissions. If you make multiple

submission, we will grade your latest valid submission. Submission after deadline
is considered as invalid.

5. D2L will send you a “Dropbox submission receipt” to confirm your submission. So

please do check your emails to make sure your submission is successfully

received. If you don’t receive a confirmation email, try again later and contact
your TA if it always fails.

6. Please take into account all kinds of possible technical issues and do expect a

huge traffic on the DEN website very close to the deadline which may render your
submission or even access to DEN unsuccessful.

7. Please DO NOT wait till the last 5 minutes to upload and submit because some

technical issues might happen and you will miss the deadline. And a kind
suggestion, if you still get some bugs one hour before the deadline, please make
a submission first to make sure you will get some points for your hard work!

8. After receiving the confirmation email, please confirm your submission by

downloading and compiling it on your machine. If the outcome is not what you
expected, try to resubmit and confirm again. We will only grade what you submitted
even though it’s corrupted.

9. You have plenty of time to work on this project and submit it in time hence

there is absolutely zero tolerance for late submissions! Do NOT assume that
there will be a late submission penalty or a grace period. If you submit your
project late (no matter for what reason or excuse or even technical issues),
you simply receive a zero for the project.

Grading Criteria:

Notice: We will only grade what is already done by the program instead of what
will be done.
For example, the TCP connection is established and data is sent to the AWS. But result
is not received by the client because the AWS got some errors. Then you will lose some
points for phase 1 even though it might work well.

Your project grade will depend on the following:

1. Correct functionality, i.e. how well your programs fulfill the requirements of the

assignment, especially the communications through UDP and TCP sockets.

2. Inline comments in your code. This is important as this will help in understanding
what you have done.

3. Whether your programs work as you say they would in the README file.

4. Whether your programs print out the appropriate error messages and results.

5. If your submitted codes, do not even compile, you will receive 5 out of 100 for the

project.

6. If your submitted codes compile using make but when executed, produce runtime
errors without performing any tasks of the project, you will receive 10 out of 100.

7. If you forget to include the README file or Makefile in the project tar-ball that you

submitted, you will lose 15 points for each missing file (plus you need to send the
file to the TA in order for your project to be graded.)

8. If your code does not correctly assign the TCP or UDP port numbers (in any phase),

you will lose 10 points each.

9. You will lose 5 points for each error or a task that is not done correctly.

10. The minimum grade for an on-time submitted project is 10 out of 100, assuming
there are no compilation errors and the submission includes a working Makefile
and a README.

11. There are no points for the effort or the time you spend working on the project or
reading the tutorial. If you spend about 2 months on this project and it doesn’t even
compile, you will receive only 5 out of 100.

12. You must discuss all project related issues on Piazza. We will give those who

actively help others out by answering questions on Piazza up to 10 bonus points.
(If you want to earn the extra credits, do remember to leave your names visible to
instructors when answering questions on Piazza. Also, you will NOT get credit by
repeating others’ answers.)

13. The maximum points that you can receive for the project with the bonus points is

100. In other words the bonus points will only improve your grade if your grade is
less than 100.

14. Your code will not be altered in any ways for grading purposes and however it will

be tested with different inputs. Your designated TA runs your project as is,
according to the project description and your README file and then check whether
it works correctly or not. If your README is not consistent with the description, we
will follow the description.

Cautionary Words:

1. Start on this project early!!!

2. In view of what is a recurring complaint near the end of a project, we want to make
it clear that the target platform on which the project is supposed to run is the
provided Ubuntu (16.04). It is strongly recommended that students develop their
code on this virtual machine. In case students wish to develop their programs on
their personal machines, possibly running other operating systems, they are
expected to deal with technical and incompatibility issues (on their own) to ensure
that the final project compiles and runs on the requested virtual machine. If you do
development on your own machine, please leave at least three days to make it work
on Ubuntu. It might take much longer than you expect because of some
incompatibility issues.

3. You may create zombie processes while testing your codes, please make sure you

kill them every time you want to run your code. To see a list of all zombie processes,
try this command: >>ps –aux | grep ee450
Identify the zombie processes and their process number and kill them by typing
at the command-line: >>kill -9 processnumber

Academic Integrity:

All students are expected to write all their code on their own.

Copying code from friends is called plagiarism not collaboration and will result in an F
for the entire course. Any libraries or pieces of code that you use and you did not write
must be listed in your README file. All programs will be compared with automated tools
to detect similarities; examples of code copying will get an F for the course. IF YOU
HAVE ANY QUESTIONS ABOUT WHAT IS OR ISN’T ALLOWED ABOUT
PLAGIARISM, TALK TO THE TA. “I didn’t know” is not an excuse.

EE450 Socket Programming Project, Fall 2018 Due Date: Thursday Nov 16th, 2018 11:59 PM (Midnight)
Problem Statement:
Source Code Files
More Detailed Explanations:
Phase 2A: (40 points)
Phase 2B: (30 points)
Phase 3: (15 points)
Required Port Number Allocation
Example Output to Illustrate Output Formatting:
Please note that the number in the example output is for display only, not a real result.
Backend-Server B Terminal:
Backend-Server C Terminal:
AWS Terminal:
Client Terminal:
Monitor Terminal:
Assumptions:
Requirements:
Programming platform and environment:
Programming languages and compilers:
Submission Rules:

Submissions WITHOUT README AND Makefile WILL BE SUBJECT TO A SERIOUS PENALTY
Makefile tutorial:
>> tar cvf ee450_yourUSCusername_session#.tar *

Any compressed format other than .tar.gz will NOT be graded!
9. You have plenty of time to work on this project and submit it in time hence there is absolutely zero tolerance for late submissions! Do NOT assume that there will be a late submission penalty or a grace period. If you submit your project late (no m…
Cautionary Words:
Academic Integrity: