active resources (displayed now in any View)īy default, before accessing an external resource, Glide searches for a suitable image at these levels in order.The cache scheme in Glide is more complex. Another attribute – NetworkPolicy.OFFLINE – instructs Picasso to download data only from the cache, without accessing the network.įor example, such a request will force Picasso to constantly download images from the network. Its NetworkPolicy.NO_CACHE and NetworkPolicy.NO_STORE attributes work the same as in MemoryPolicy. With the help of the second, the disk cache is regulated.
The first allows you to refuse to access the online cache during image loading (attribute MemoryPolicy.NO_CACHE) or not to save the downloaded image to the cache (attribute MemoryPolicy.NO_STORE). The functions memoryPolicy() and networkPolicy() are used to control them. Picasso supports 2 types of cache by default: LRU cache size of 15% of the RAM available to the application, and disk cache size from 5 to 50 MB (depends on the available size of read-only memory). It would be more interesting to compare the advanced features of Picasso, Glide and Fresco: caching and image transformation, as well as unique tools of each library. The second significant feature of Fresco is the use of its own SimpleDraweeView instead of the traditional ImageView.Ĭomparison of the simple functions of these libraries (loading resources, error handling, placeholders) will not bring much value to the Android developer, as these functions are intuitive and easy to learn in just an hour. Now the gap has narrowed, but Fresco still continues to lead in this setting. Especially significant was its advantage over other image downloaders on devices with Android 4. When loading images, this library focuses on working efficiently with memory and productivity.
0 kommentar(er)
