Phil Sturgeon.co.uk
There's no place like 127.0.0.1!
Navigation
Thoughts
Recent Posts
CodeIgniter "2.0": Rumours, facts and requests
Ever since it was announced that ExpressionEngine 2.0 would be running on CodeIgniter, the forums have been jammed full of "CodeIgniter 2.0" questions. I have answer this so many times I wanted to clear things up and put some useful suggestions forward.
Speaking at EECI2009 in Leiden, Holland
As a massive fan of CodeIgniter I was pretty excited to be attending the EECI2009 conference in Leiden, Holland, as it would give me the chance to meet the EllisLabs development team and lots of other CodeIgniter nerds. Now as a last minute replacement I will actually be speaking at the event too!
Asset handling in CodeIgniter with the BASE tag
There are many suggested ways to handle your assets in CodeIgniter (including my very own Asset library) but this solution has to be one of the easiest. Read on to find out what it is!
Clearing CodeIgniter session data
This article shows a few ways of clearing session data in CodeIgniter, inlcuding a non-documented approach which lets you wipe all session data without destroying the session.
UTF-8 support for CodeIgniter
Writing a CodeIgniter application is easy. Writing a CodeIgniter application that supports all characters from multiple languages? Not so easy. Find out how to support UTF-8 content in CodeIgniter.
REST implementation for CodeIgniter
Posted: Jun 03, 2009
Category: CodeIgniter
I have seen 1 or 2 RESTful implementations for CodeIgniter but the syntax and methodology for each of them left me feeling like it could be done better.
Firstly, REST is not something that can be put into a library. It is not a "thing" and cannot be treated as such.
Secondly, REST calls should not be mixed in with your normal controllers. It should be kept separate from your normal controllers as they are not the same. The default behavior should be slightly different as REST calls are not simple GET -> output.
Thirdly, REST controllers need to remain flexible. For that reason the normal CodeIgniter URI segments are not enough. To keep the controllers flexible, associative URI segments should be enforced so any combination of parameters can be used.
Finally, REST controllers should be able to output the response in many number of formats. These formats should be specified by the requester and not set in stone within the code. This means a REST controller needs to detect the desired format in two different ways.
- via the $_SERVER['HTTP_ACCEPT'] variable. This will allow cURL, telnet, etc to specify a method through standard HTTP headers. This is the recommended REST way.
- via the URL. This allows browsers and systems not using cURL, telnet, etc to make very basic requests to receive different formats.
- via the controller. Adding "public $rest_format = 'json';" will make that one controller default to json if nothing is provided by given via URL or HTTP_ACCEPT.
It took a great deal more thought and consideration than it did actual implementation. Here is the code I have used to get my CodeIgniter RESTful implementation working, tested and complete.
application/libraries/REST_Controller.php - This new controller type will contain all of the logic for our new REST controllers.
application/config/rest.php - Control login restrictions and caching for your REST server.
application/controllers/example_api.php - This is an example of a REST controller with some basic user data. This can be called anything you like and be placed in Matchbox modules, sub-directories, whatever.
Useage
Now it is all set up and ready go. Crack open your browser and try URL's in these formats to see what happens:
Get one users profile
http://localhost/codeigniter/index.php/example_api/user/id/435
Get a list of users in HTML format
http://localhost/codeigniter/index.php/example_api/users/users/format/html
Try to access an object through an unsupported method
http://localhost/codeigniter/index.php/example_api/user_put/id/435/name/Something
Personally, I would recommend using Matchbox to get your controllers into modules and then put a api.php controller into each module you wish to send over the API.
E.g http://localhost/codeigniter/index.php/news/api/article/id/465
As you can see there is plenty of flexibility here. You can use any of the following formats too simply by appending /format/json to the end of your URL or passing the correct MIME-type:
- xml
- json
- serialize
- php (raw output that can be used in eval)
- html
- csv
Within your REST controllers, remember you can access GET parameters through $this->get(), POST parameters through $this->post() and PUT parameters through $this->put().
Let me know what you think of this in the comments, tweet me or use the contact form.
