Cache for PUT and POST request

[tamtakoe]

Make, please, so that when you add or update an instance of the resource the associated cache would be updated.

[btford]

As part of our effort to clean out old issues, this issue is being automatically closed since it has been inactivite for over two months.

Please try the newest versions of Angular (1.0.8 and 1.2.0-rc.1), and if the issue persists, comment below so we can discuss it.

Thanks!

[zuzusik]

Request for this to be reopened.

As for now, when using ngResource, when updating resource (making put request), the cache is not being updated and when getting this resource, you get the old one from cache.

[gabzim]

+1.. I don't want to overwrite all method and provide transformResponse functions just to invalidate the cache. I feel angular should take into account POST and PUT requests. or at least provide a sort of "invalidateCacheWhenPost" (hopefully not such a horrible name) flag when declaring custom functions.

[quantizor]

Why would you want to cache PUT and POST? They're meant for transmitting data and should be fresh every time to capture the changed result.

[gabzim]

When I mean take into account POST and PUT requests, I mean that they should invalidate the cache. The way I'm doing it now is overriding save and invalidating the cache on transformResponse if the post was successful. I feel angular should provide a mechanism to do this (so long as you're using the standard cache for $http) out of the box without having to provide a custom implementation.

[quantizor]

Oh I see, so you mean that a non-GET request on ID 1 would invalidate the cache for a GET request on ID 1.

I think this is a worthy addition to ngResource, perhaps under a boolean flag. What do you think @caitp? Seems like it'd be achievable with very little added code - look if a cacheFactory was supplied and if not, remove the requested URL from the httpDefaultCache.

[Aaronius]

+1 for this to be re-opened. I was hoping for the same as what is being described.

[rhurling]

i would really like to see this as well, the query cache seems to be cleared if a new entry is added/deleted

[halukugurlu]

We are using post requests to retrieve data from a Druid back-end storage system. Our queries sent/received in JSON format, most queries tend to be lengthy JSON files (more than the maximum length GET can handle). So for that reason we are using POST to send a post req. It's also the requirement to communicate with Druid database. It would be very nice if we could use this caching feature. Because, our users usually query old ranged data, which doesn't change in real time.

[SushantKadam008]

HI,
Is there a way to implement the same ?
My requirement is also on the same lines of halukugurlu