Closed holtwick closed 12 years ago
You should do the caching in your code. IMO, networking frameworks should cache based on HTTP Headers and not based on application logic. One application's logic might not work with another. For example, in your case, how do you control cache expiry of a a resized/cropped image?
Ok, you're probably right. I thought it would have made sense to use the caching infrastructure of MKNetworkKit. By just replacing the response data with the data of a processed image it might have used the same cache expiry behaviour.
Hi, I love this project. Awesome work!
Image loading works great. But in my app I do some image manipulation before dsplaying the thumbnail, like resizing, croping, removing alpha and adding a border. It would be great to cache this, because it would have some advantages:
I was not able to find a good place where to add this step in your code, therefore I add this feature request to get your help. Or should I better do the caching in my code?
This is how the competion solves the problem ;) https://github.com/AFNetworking/AFNetworking/blob/master/AFNetworking/AFImageRequestOperation.m#L107