RESTful Rails for Ajax

Ruby on Rails 1.2 added full support for building RESTful services to the already nice web page support. REST is a conceptually simple idea, yet incredibly powerful. REST is a Web based API to an application. It builds on the basic building blocks of HTTP: URLs and HTTP Methods (think verbs).

A URL (Uniform Resource Locator) uniquely identifies a resources on the web. HTTP uses the concept of Methods to give context to a request to a URL. Most developers will be familiar with a GET and a POST. These methods are used to get a resource and to modify a resource respectively. But there are other http verbs as well. The two other interesting ones for a REST service are PUT and DELETE. Both of these are pretty self explanatory. PUT creates a resource at the remote location and DELETE removes one.

For Example:


Both of these use the same URL, but the HTTP Method means different things will happen.

Creating A RESTful API with Rails

Rails makes it easy to create a RESTful application. The same controllers can be used to render a web page and to provide a programmatic API to your application.

Rails provides a scaffold_resource generator that creates the skeleton of a resource driven application:

./script/generate scaffold_resource order

This creates Model, View and Controllers just like regular scaffold, but unlike scaffold, it adds some extra functionality.

class OrdersController < ApplicationController # GET /orders/1 # GET /orders/1.xml def show @order = Order.find(params[:id]) respond_to do |format| format.html # show.rhtml format.xml { render :xml => @order.to_xml }

Now if you request a path ending in .xml it will render the response as an XML document that can be consumed by another program.

Applying REST as an Ajax solution

The great news is that you can use this RESTful API directly as an API to use for building a highly-dynamic Ajax application. (See my post on using Ajax with PHP for an example). But what’s even cooler is that you can use the same technique to build a JSON API. JSON is much easier and less resource intensive to consume in an Ajax application than XML.

Changing your controller to support JSON ends up being really easy. All you have to do is add a single line in the respond_to block to support it:

class OrdersController < ApplicationController # GET /orders/1 # GET /orders/1.xml # GET /orders/1.js def show @order = Order.find(params[:id]) respond_to do |format| format.html # show.rhtml format.xml { render :xml => @order.to_xml }
format.js { render :json => @order.to_json }

Just like in the XML example, if you make a request that ends in .js then you will get a response rendered as JSON. Consuming that JSON Service with something like Dojo allows you to easily create a dynamic web application.


function getOrder(id) {{url: "/orders/" + id + ".js", handler: showOrder, mimetype: "text/json"});

function showOrder(type, data, evt) {
appendOrderPart('order_number', data.attributes.order_number);
appendOrderPart('time', data.attributes.time);
dojo.lfx.highlight(dojo.byId('order'), dojo.lfx.Color);
function appendOrderPart(id, value) {
var element = document.createElement("div");;
function init() {



With a few simple lines of code you can not only render a web page, you can also create an XML API and a JSON API. That’s what I call developer friendly!

Ajax with JSON using PHP and DOJO

Buzzword alert! Buzzword alert! Synergisticly expedite transparent web-readiness! Buzzword alert! Buzzword alert!

Ok, now that I’ve got that out of the way…

Ajax is a web application development architecture that resembles more of a client-server architecture than traditional web development. In an Ajax application a client application is delivered to the browser consisting of HTML, CSS and JavaScript. The interactions of the client with the server send and receive data, data that the client then knows how to display to the user.

While Ajax has an ‘X’ which stands for XML in its name, Ajax really has nothing to do with XML at its core. In reality parsing XML is usually a lot more work than you need to do when you expect that a client will be a browser. Along comes JSON. JavaScript Object Notation is a structured format that corresponds to the needs of the client-side programming environment: JavaScript. JSON can be evaluated on the client into JavaScript object graphs, no parsing, no XML Sax or DOM parsing, just eval() into a JavaScript object and then call methods on it.

Ajax, as a hot technology, I was of course interested in learning more so I created a small example application that I could build and play with a bit. I thought I’d share it with everyone so they could use it as a quick-start example for trying some of these technologies.

I chose to use the DOJO Toolkit as my client-side framework because it seems to have a very broad library already built and a reasonable amount of documentation. DOJO is really engineered like a true software application. It really shows off the fact that you can write good code and good frameworks using the JavaScript language.

Show Me Some Code

Here’s an example of a simple blog application that talks to a single table to display articles.


A very simple HTML skeleton that imports the CSS, DOJO and the Application written in JavaScript.


    The Application that is delivered to the Client.

    getArticle() is called and initiates an asynchronous call to the getArticle.php code. When the response comes back DOJO automatically calls the showArticle() function and passes the response data to it. The showArticle() function handles formatting the data by manipulating the HTML DOM of the page.

    function getArticle(id) {
    var idStr = "{\"id\":" + id + "}";
    request = {'action' : 'getArticle', 'data' : idStr};{
    url: "getArticle.php",
    handler: showArticle,
    mimetype: "text/json",
    content: request
    function showArticle(type, data, evt) {
    appendArticlePart('title', data.title);
    var date =;
    appendArticlePart('content', data.content);
    dojo.lfx.highlight(dojo.byId('article'), dojo.lfx.Color);
    function appendArticlePart(id, value) {
    var element = document.createElement("div");;


    The code that lives on the server and responds to a given service request. This PHP code parses the HTTP request that the DOJO toolkit sends to the server. It parses the data from a JSON string into PHP objects, calls into the database and gets some values out. It then turns a PHP array into a JSON string to return to the web client.

    $article = getArticle($jsonArray);
    print $json->encode($article);
    function getArticle($node) {
    $result = null;
    $link = connect_db();
    if ($stmt = $link->prepare("select id, title, publish_time, content from articles where id=?")) {
    $stmt->bind_param("i", intval($node->id));
    $stmt->bind_result($id, $title, $time, $content);
    if ($stmt->fetch()) {
    $result = array(
    "id"=> $id,
    "title" => $title,
    "time" => $time,
    "content" => $content,
    "objectId"=> "article"
    return $result;
    function connect_db() {
    $mysqli = new mysqli("localhost", "root", null, "blog");
    /* check connection */
    if (mysqli_connect_errno()) {
    printf("Connect failed: %s\n", mysqli_connect_error());
    return $mysqli;

    While this example is written in PHP, there is nothing that would prevent you from writing the server component in any language. There are JSON libraries for every language you’ve ever heard of (and a lot that you’ve never even heard of). The notation itself is fairly simple (it’s about 700 lines of code in PHP), so implementing it in another language should be relatively easy as well.

    Consider using implementation neutral URIs for your service calls and then using something like Apache mod-rewrite to map those URIs to the proper calls in whatever language you use to implement the server code. Doing this and you should be able to completely decouple your web client from the server components.


    DOJO Toolkit
    Dojo: The Definitive Guide
    Mastering Dojo: JavaScript and Ajax Tools for Great Web Experiences (Pragmatic Programmers)