Resource cache just passes cache to $http, but doesn't cache instances

[elado]

Seems like cached actions might be cached on $http level, but the resource instances are re-created every time. This obviously uses more memory, and also an unexpected behavior.

If I have a simple Category resource with cached query action, and I call Category.query() from multiple directives, it does loads them all at once (expected) but instances in every place are different. Editing one instance on a directive (as an ngModel or whatever) doesn't affect the others. As a temporary solution I can wrap the query function and handle the caching myself but would be great if angular-resource took care of it.

(Using latest 1.3 beta)

https://github.com/angular/angular.js/blob/master/src/ngResource/resource.js#L567

[elado]

A current workaround of mine is to wrap the query function, call the actual method only once and prevent incoming calls until resolved: https://gist.github.com/elado/a6f5f1f8edade63a3b9d

[jimmywarting]

Possible related to #866?
I can think of several reasons why you would and wouldn't want to use the same Instance...

How about using the same instance from $rootScope.result or a service instead of calling Category.query() multiple times from different directives? wouldn't that be more convenient?

[elado]

@jimmywarting Sure, I can use a service, but I have to queue up myself the callbacks (exactly like I did in the gist). When I use cache: true, I expect the resource to cache it internally and queue up all the callbacks, like $http does.

Using the same instances will save a lot of memory in complex applications.

All the resources that don't change frequently are the best use-case. Categories, countries etc., but it can be used anywhere with the proper invalidation mechanism.