SDWebImage #163
Description
Hey all,
I'm aware Fast Image Cache is the absolute fastest way to go from image data on disk to being rendered by Core Animation. Could we in theory use NSURLConnection or one of many popular networking libraries (like AFNetworking) to actually download the image data from our server in batch, then use SDWebImage.
With that in mind, or option2: As it stands today should we still use Fast Image Cache to have it optimize it for future rendering? This is basically to stop some performance bottlenecks—especially with scrolling—as a result of images need to display quickly while scrolling (obviously.)