This SitePoint series has explored REST principles. This article demonstrates building a RESTful web service using Slim, a PHP micro-framework inspired by Sinatra (Ruby). Slim's lightweight nature, with core components like routing, request/response handling, and minimal view support, makes it ideal for simple REST APIs.
Key Concepts:
post()
, put()
, and delete()
methods for creating, updating, and deleting book records respectively.Introducing Slim:
Begin by downloading Slim. This example uses the 5.3 style. Create index.php
:
get("/", function () {
echo "Hello Slim World
";
});
$app->run();
?>
Accessing index.php
in your browser displays "Hello Slim World". Slim autoloads necessary files. The Slim constructor accepts configuration (e.g., MODE
, TEMPLATES.PATH
, VIEW
). MODE
sets the environment (development/production), and TEMPLATES.PATH
specifies the template directory. Custom view handlers can replace the default Slim_View
. Example:
"development",
"TEMPLATES.PATH" => "./templates"
));
?>
Route creation is crucial. Routes map URIs to callback functions based on HTTP methods. Slim prioritizes the first matching route; unmatched requests result in a 404 error. After defining routes, call run()
to start the application.
Building a Library Service:
Let's create a library management service. NotORM simplifies database interaction (requires a PDO instance).
Listing Books:
This endpoint lists all books in JSON format:
get("/books", function () use ($app, $db) {
$books = array();
foreach ($db->books() as $book) {
$books[] = array(
"id" => $book["id"],
"title" => $book["title"],
"author" => $book["author"],
"summary" => $book["summary"]
);
}
$app->response()->header("Content-Type", "application/json");
echo json_encode($books);
});
// ... (rest of the code) ...
get()
handles GET requests. use
allows accessing external variables within the anonymous function. The response header is set to application/json
, and the book data is encoded as JSON.
Getting Book Details:
Retrieve a book by ID:
get("/book/:id", function ($id) use ($app, $db) {
$app->response()->header("Content-Type", "application/json");
$book = $db->books()->where("id", $id);
if ($data = $book->fetch()) {
echo json_encode(array(
"id" => $data["id"],
"title" => $data["title"],
"author" => $data["author"],
"summary" => $data["summary"]
));
} else {
echo json_encode(array(
"status" => false,
"message" => "Book ID $id does not exist"
));
}
});
// ... (rest of the code) ...
The route parameter :id
is passed to the callback function. Optional parameters use /book(/:id)
. For optional parameters without explicit callback arguments, use func_get_args()
.
Adding and Editing Books:
post()
adds, and put()
updates books:
post("/book", function () use ($app, $db) {
$app->response()->header("Content-Type", "application/json");
$book = $app->request()->post();
$result = $db->books->insert($book);
echo json_encode(array("id" => $result["id"]));
});
$app->put("/book/:id", function ($id) use ($app, $db) {
$app->response()->header("Content-Type", "application/json");
$book = $db->books()->where("id", $id);
if ($book->fetch()) {
$post = $app->request()->put();
$result = $book->update($post);
echo json_encode(array(
"status" => (bool)$result,
"message" => "Book updated successfully"
));
} else {
echo json_encode(array(
"status" => false,
"message" => "Book id $id does not exist"
));
}
});
// ... (rest of the code) ...
$app->request()->post()
and $app->request()->put()
retrieve POST and PUT data respectively. For browser-based PUT requests, use a hidden field _METHOD
with value "PUT" in your form.
Deleting Books:
Delete a book by ID:
delete("/book/:id", function ($id) use ($app, $db) {
$app->response()->header("Content-Type", "application/json");
$book = $db->books()->where("id", $id);
if ($book->fetch()) {
$result = $book->delete();
echo json_encode(array(
"status" => true,
"message" => "Book deleted successfully"
));
} else {
echo json_encode(array(
"status" => false,
"message" => "Book id $id does not exist"
));
}
});
// ... (rest of the code) ...
The delete()
method removes the database record. The map()
method handles multiple HTTP methods on a single route (not shown here).
Conclusion:
This article demonstrates building a basic RESTful web service with Slim. Further development should include robust error handling and input validation. The source code (not included here) can be found on GitHub (link not provided in original text). The FAQs section of the original text is omitted as it provides basic information readily available through Slim's documentation.
Disclaimer: All resources provided are partly from the Internet. If there is any infringement of your copyright or other rights and interests, please explain the detailed reasons and provide proof of copyright or rights and interests and then send it to the email: [email protected] We will handle it for you as soon as possible.
Copyright© 2022 湘ICP备2022001581号-3