Both are right. `Ember.ajax` isn't designed to pass the data directlly, instead it will retrieve all the info in a single object. 

    Ember.getJSON('/posts').then(function(evt) {
      // evt.xhr, evt.data etc
    });

Without this, users will fallback in `jQuery.ajax`, because they could not do something with the `Ember.ajax`. E.g extract some header from xhr object.

But the next implementation, maybe `Ember.getJSON`, will be aware of json payload, so the following will work:

     model: function() {
       return Ember.getJSON('/posts');
     }

This will be the common case. `Ember.ajax`, is intended to rare ones.

I am just concerned about the `Ember.getJSON`, because this is just to retrieve json data. I think that we need something to send json. With the `Ember.ajax` will be possible, but the headers `application/json` will need to be setup all the time. So I am thinking in some `Ember.sendJSON(url, [method], [options])`:

    // defaults to get
    Ember.sendJSON('/posts').then(function(posts) {
      // posts => [ { id: 1, title: rails is omasake ... } ]
    }).fail(function(evt) {
      // same like Ember.ajax. evt.xhr, evt.data etc
    });


A post request

    Ember.sendJSON('/posts', 'POST').then(function(post) {
      // post => { id: 1, title: rails is omasake ... }
    }).fail(function(evt) {
      // same like Ember.ajax. evt.xhr, evt.data etc
    });

`Ember.getJSON(url)` can be an alias to `Ember.sendJSON(url, 'GET')`.

Thoughts?