PA 24.1 (Advanced): CalPal with REST

Take a look at CalPal Download CalPal, which is a calendar web application. Currently, it uses an ad-hoc API to perform CRUD operations on the server.  Update it so that the server code exposes a RESTful API and then update the client to use that API.

Here's the rubric:

[ ] from the user's perspective, CalPal behaves as it did with the ad-hoc API
[ ] all requests are made in a RESTful manner
    [ ] operations are determined based on the HTTP method and the URI
    [ ] ids are embedded in the URI
[ ] all responses generated adhere to the REST constraints
    [ ] the Location field of the response is used to store the URI of a resource created with a POST request
    [ ] HTTP errors are used to indicate request failure
[ ] the code is well commented and styled
[ ] there is a header at the top of the file that includes the name of the author(s) and a brief description of the file
[ ] the PA folder includes a README.md file with the required information in it 

Submitting PAs

Be sure to create a README.md with the following information:

• who you worked with (say "I worked alone" if you didn't have a partner)
• how long you spent on the assignment
• the PA option (and, if applicable, the earlier PA option it builds off of)
• a copy of the PA option's rubric, filled out (only submit if you can honestly check off each of the criteria)
• what the most challenging aspects were
• any lingering questions you have about the assignment

Commit and push your git repository to GitHub, then paste a link to your PA directory.