You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.)
The text was updated successfully, but these errors were encountered:
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 (likeAFNetworking
) to actually download the image data from our server in batch, then useSDWebImage
.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.)
The text was updated successfully, but these errors were encountered: