14. JsonP P w/ padding Uses callback Cross domain <?php if ( $callbackFunc !== false ) echo $callbackFunc.'('; echo $content_for_layout; if ( $callbackFunc ) echo $callbackFunc.')'; ?> function beforeFilter() { if ( array_key_exists('callback’, $this->params[‘url’]) ) $this->set(‘callbackFunc’, $this->params[‘url’][‘callback’]); else $this->set(‘callbackFunc’, false); } APP/views/layouts/json/default.ctp APP/app_controller.php
15. XML View Strongly Typed Human readable Lots of existing tools <? echo ‘<url>’; echo $xml->serialize( $url ); echo ‘<url>’; ?> APP/views/urls/xml/view.ctp
16. Other Views Human Readable XML Json / JsonP HTML YAML CSV Serialized PHP Etc… Binary AMF Microsoft Excel PDF JPEG / PNG Etc…
17. Testing It Out Using cURL Create curl –d “url=www.example.com” http://tinyr.me/urls.json Read curl http://tinyr.me/urls/123.json Update curl –d “url=www.example.com/foo” http://tinyr.me/urls/123.json Delete curl –X DELETE http://tinyr.me/urls/123.json
18. Done? We have MVC files RESTful Views XML Json / JsonP We’re missing Error handling Pagination Authentication Authorization Documentation
19. Status Codes Success 200 OK * 201 Created * 303 See Other * Error 401 Unauthorized * 402 Payment Required 403 Forbidden * 404 Not Found * Error (continued) 405 Method Not Allowed * 409 Conflict 410 Gone 500 Internal Server Error 501 Not Implemented 503 Service Unavailable
20. Add Method If not a POST request 405 Method Not Allowed Already existed 303 See Other Save success 201 Created Failure 200 OK with explanation
21. Edit Method If not a POST or PUT request 405 Method Not Allowed Invalid ID 404 File Not Found Success 200 OK Failure 200 OK with explanation
22. Delete Method If not a POST or DELETE request 405 Method Not Allowed Invalid ID 404 File Not Found Success 200 OK Failure 200 OK with explanation
23. Global User is not allowed to access resource 403 Forbidden User is not logged in 401 Unauthorized
Who am I.Introduce myVBO.About this presentation.What I’ll talk about.
Neil – plugins to consumeNot much code.Overview.All the slides will be online right after lunch.
Raise your hand up if you use CakePHP to handle some kind of data.Now put your hand down if you don’t have an API.If you have info why not be a platform?It doesn’t matter if the platform is very simple. A blog is a platform. It has an API for posting new articles and it has an RSS feed for syndicating them.Now that I simplified it.That’s my take.
Even if you are developing a closed API…I hope everyone considers open APIs.All this roles up into one concept. “The platform play.” So if you need something to go back to your boss or your investors with… that’s the thing. You’re making a platform play.
If this was five years ago...But the strategy works pretty well. TwitterFacebookBit.lyAmazonandSalesforceNow it is almost a necessity to have an API of some sort.
There are multiple patterns for APIs. There are a couple more lesser used ones but the two big ones are REST and RPC.Within those patterns you can use one or more formats to transfer your data.
Rest stands for Representational State Transfer incase you missed it in Neal’s presentation. As mentioned yesterday, the largest example of REST in the wild is HTTP.Luckily for us, CakePHP is usually layered on-top of HTTP so it inherits all the RESTful mechanisms.REST has a concept called resources (a specific user or comment are two examples).They are also called nouns which are acted on by verbs.There are five verbs in HTTP. We will focus on three.Finally, one last important thing… CakePHP makes REST easy.
The app that I will be using as an example today is the simplest app that I could think of.It is a URL shortening services that allows you to authenticate and thus be able to delete and edit URLs that you yourself shortened, and also basic CRUD.
There are two models. The user model, which is pretty standard for a CakePHP project, and the urls model which I have on the screen.A full URL shortened can, of course, get much more complicated than that. But for today I’m keeping it basic.
Once you’ve baked your model and what not you can open up your router and map the resource. This will register all the routes you need for REST in one call.You can still do it manually if you want but you don’t have to.These are the six routes registered when you map a resource.
One rule to live by is to never write or delete data on anything that is not a POST, PUT, or DELETE request.The main purpose of this rule is to protect against Cross Site Request Forgeries or CSRF attacks which are every difficult to defend against otherwise.Say that the add method accepted GET requests. Someone could then simply embed an image on a page with the add URL as a source and execute a add() as any user who visits the site.
Before we begin developing views we’ll haveto tell PHP to recognize file extensions and switch the views and layouts accordingly.We do this by turning on parseExtensions in the routes.php file and including the RequestHandler component in the app_controller.The RequestHandler component is what actually switches the views. It also includes helpers automatically in the view if a helper has the same name as the extension (like XML) and parses incoming POSTed XML and assigns it to the data property of the controller.
We now need to create a couple views.The Json view is the first and the one that I like the most. Because it is simple and easy to understand.It is fast thanks to native PHP support, and also very wide-spread.What you see here is the entire view for the view action in the urls controller.Notice the path to the view. The RequestHandler will tell Cake to look in the json folder for the appropriate view.
We can also easily support JsonP or Json with padding.JsonP specifies a Javascript callback function to execute with the results of a request.It allows for cross domain requests because you can trigger it via a simple script-include and function calls works across domains so the callback will work just fine.One important note is that it is only for GET requests. So, as I said earlier, it shouldn’t be able to write or delete data.JsonP can be handle generically in the layout. Notice the layout path.A JsonP request always takes the callback via a query parameter. So your app controller can read in the callback then set it for use in the view. The layout then reads it sand wraps the output in it is necessary.
Now for the XML view. And I can hear the boos now.XML does have some benefits. It is strongly typed, human readable, and has lots of existing tools available.Like Json, the view is pretty self-explanatory. Note the xml sub-directory in the view path.
One of the best parts about using parseExtensions and RequestHandler is you can literally have as many views as you want into the data.I listed just some of them here.
Erik’s talk.
If you did the ACL stuff Erik was talking about…Little difficult. Default behavior is redirectController, model, and object
