$30
Assignment No. 5
EECS 368
Programming Language Paradigms
Deliverables:
1. Copy of Rubric5.docx with your name and ID filled out (do not submit a PDF)
2. JavaScript code for the HTTP server specified below.
How to submit the Assignment?
• Please review the student demo video at the link below. It will tell you how
you can create, test, and submit your assignment. If you have any questions,
please contact our SI, Soujanya Ambati at: saisoujanyaambati@ku.edu.
https://drive.google.com/drive/folders/1n1R5b3YihQcbCVyQwUjVBD1IMGMdEvBE
Assignment:
• Using what you learned in Chapter 20 about Node.js, write the JavaScript code
for an HTTP server that allows remote access to a file system.
• Use the HTTP methods GET, PUT, and DELETE to read, write, and delete files
on the server, respectively.
• Then, add support for the MKCOL method (“make collection”), which should
create a directory by calling mkdir from the fs module.
• MKCOL is not a widely used HTTP method, but it does exist for this same
purpose in the WebDAV standard, which specifies a set of conventions on top of
HTTP that make it suitable for creating documents.
• The server should include code to detect an invalid request and return a status
code of 405 with the message "The method XXX is not supported.", where XXX
is the invalid method requested.
• Feel free to use code you find on the Internet. Just be sure to include comments
that adequately describe the code.
• Provide comments for the JavaScript code that explain what each line of code is
doing. See rubric below.
Rubric for Program Comments
Exceeds Expectations
(90-100%)
Meets Expectations
(80-89%)
Unsatisfactory
(0-79%)
Software is adequately
commented with prologue
comments, comments
summarizing major blocks of
code, and comments on every
line.
Prologue comments are present
but missing some items or some
major blocks of code are not
commented or there are
inadequate comments on each
line.
Prologue comments are missing
all together or there are no
comments on major blocks of
code or there are very few
comments on each line.
Adequate Prologue Comments:
• Name of program contained in the file (e.g., EECS 368 Assignment 3)
• Brief description of the program, e.g.:
o Simple tabbed interface using JavaScript and HTML
• Inputs (e.g., none, for a function, it would be the parameters passed to it)
• Output, e.g.,
o Browser window with 3 tabs and text
• Author’s full name
• Creation date: The date you first create the file, i.e., the date you write this
comment
Adequate comments summarizing major blocks of code and comments on every line:
• Provide comments that explain what each line of code is doing.
• You may comment each line of code (e.g., using //) and/or provide a multi-line
comment (e.g., using /* and */) that explains what a group of lines does.
• Multi-line comments should be detailed enough that it is clear what each line of
code is doing.
Remember:
• Your Programming Assignments are individual-effort.
• You can brainstorm with other students and help them work through problems in
their programs, but everyone should have their own unique assignment programs.