Handling Requests and Responses

Now that we have created the first route, the second step is to determine what properties you will need while handling the requests that you are receiving, while also creating other routes. With that being said, it is really important to return meaningful responses so that you can change/update application states. This chapter also covers methodologies that will be helpful when testing the application, such as not directly using the request/response parameters in methods. We will also describe response status codes and when to use which status code.
Not every URL is pure and plain when requesting data. In this chapter, we are going to create a mapper that handles and calls the correct controller according to the URL's resource. Most of the time, URLs also have some query strings or additional paths for filtering data, and have a paginated output...