Notes

$http vs $resource dev discussion

$resource let you communicate with a server using custom actions instead of relying on the default get, post, delete, etc. Those custom actions are bound to the default HTTP method. “Get" is using the method GET while “save" is using the method POST etc. Keep in mind that this service comes from the module “ngResource". As such, your module will need a dependency to “ngResource" in order to let you inject "$resource" in your code.

$resource(url[, paramDefaults][, actions]) returns A resource "class" object with methods for the default set of resource actions optionally extended with custom actions. The default set contains these actions:
{ 'get': {method:'GET'},
'save': {method:'POST'},
'query': {method:'GET', isArray:true},
'remove': {method:'DELETE'},
'delete': {method:'DELETE'}
};

It is important to realize that invoking a $resource object method immediately returns an empty reference (object or array depending on isArray). Once the data is returned from the server the existing reference is populated with the actual data. This is a useful trick since usually the resource is assigned to a model which is then rendered by the view. Having an empty object results in no rendering, once the data arrives from the server then the object is populated with the data and the view automatically re-renders itself showing the new data. This means that in most case one never has to write a callback function for the action methods. The action methods on the class object or instance object can be invoked with the following parameters:

HTTP GET "class" actions: Resource.action([parameters], [success], [error])
non-GET "class" actions: Resource.action([parameters], postData, [success], [error])
non-GET instance actions: instance.$action([parameters], [success], [error])

http://www.bennadel.com/blog/2433-Using-RESTful-Controllers-In-An-AngularJS-Resource.htm

http://joshua.themarshians.com/hardcore-google-communicating-angularjs.html