This recipe begins like the last one, so let's skip straight into the definition of our Service[14 to 22]:
|req: Request| {
match (req.method(), req.path()) {
(&Method::Get, "/") => handle_root(),
(&Method::Post, "/echo") => handle_echo(req),
_ => handle_not_found(),
}
}
We are now using the Request parameter that the last recipe simply ignored.
Because Rust allows us to pattern match on tuples, we can directly differentiate between HTTP methods and path combinations. We then pass on the control flow of our program to dedicated route handlers, which in turn are responsible for returning the response.
In bigger programs with tons of routes, we would not specify them all in one function, but spread them across namespaces and split them into subrouters.
The code for handle_root [29] looks nearly identical to the hello world Service from the last chapter, but instructs the caller to POST at the /post route...