[转]Android图片下载
因为国内被墙,看起来不方便,转载下,原文地址:http://android-developers.blogspot.com/2010/07/multithreading-for-performance.html
Multithreading For Performance
[This post is by Gilles Debunne, an engineer in the Android group who loves to get multitasked. — Tim Bray]
A good practice in creating responsive applications is to make sure your main UI thread does the minimum amount of work. Any potentially long task that may hang your application should be handled in a different thread. Typical examples of such tasks are network operations, which involve unpredictable delays. Users will tolerate some pauses, especially if you provide feedback that something is in progress, but a frozen application gives them no clue.
In this article, we will create a simple image downloader that illustrates this pattern. We will populate a ListView with thumbnail images downloaded from the internet. Creating an asynchronous task that downloads in the background will keep our application fast.
An Image downloader
Downloading an image from the web is fairly simple, using the HTTP-related classes provided by the framework. Here is a possible implementation:
staticBitmap downloadBitmap(String url){
finalAndroidHttpClient client =AndroidHttpClient.newInstance("Android");
finalHttpGet getRequest =newHttpGet(url);
try{
HttpResponse response = client.execute(getRequest);
finalint statusCode = response.getStatusLine().getStatusCode();
if(statusCode !=HttpStatus.SC_OK){
Log.w("ImageDownloader","Error "+ statusCode +" while retrieving bitmap from "+ url);
returnnull;
}
finalHttpEntity entity = response.getEntity();
if(entity !=null){
InputStream inputStream =null;
try{
inputStream = entity.getContent();
finalBitmap bitmap =BitmapFactory.decodeStream(inputStream);
return bitmap;
}finally{
if(inputStream !=null){
inputStream.close();
}
entity.consumeContent();
}
}
}catch(Exception e){
// Could provide a more explicit error message for IOException or IllegalStateException
getRequest.abort();
Log.w("ImageDownloader","Error while retrieving bitmap from "+ url, e.toString());
}finally{
if(client !=null){
client.close();
}
}
returnnull;
}
A client and an HTTP request are created. If the request succeeds, the response entity stream containing the image is decoded to create the resulting Bitmap. Your applications' manifest must ask for the INTERNET
to make this possible.
Note: a bug in the previous versions of BitmapFactory.decodeStream
may prevent this code from working over a slow connection. Decode a new FlushedInputStream(inputStream)
instead to fix the problem. Here is the implementation of this helper class:
staticclassFlushedInputStreamextendsFilterInputStream{
publicFlushedInputStream(InputStream inputStream){
super(inputStream);
}
@Override
publiclong skip(long n)throwsIOException{
long totalBytesSkipped =0L;
while(totalBytesSkipped < n){
long bytesSkipped =in.skip(n - totalBytesSkipped);
if(bytesSkipped ==0L){
intbyte= read();
if(byte<0){
break; // we reached EOF
}else{
bytesSkipped =1;// we read one byte
}
}
totalBytesSkipped += bytesSkipped;
}
return totalBytesSkipped;
}
}
This ensures that skip() actually skips the provided number of bytes, unless we reach the end of file.
If you were to directly use this method in your ListAdapter's getView method, the resulting scrolling would be unpleasantly jaggy. Each display of a new view has to wait for an image download, which prevents smooth scrolling.
Indeed, this is such a bad idea that the AndroidHttpClient does not allow itself to be started from the main thread. The above code will display "This thread forbids HTTP requests" error messages instead. Use the DefaultHttpClient instead if you really want to shoot yourself in the foot.
Introducing asynchronous tasks
The AsyncTask
class provides one of the simplest ways to fire off a new task from the UI thread. Let's create anImageDownloader
class which will be in charge of creating these tasks. It will provide a download
method which will assign an image downloaded from its URL to an ImageView
:
publicclassImageDownloader{
publicvoid download(String url,ImageView imageView){
BitmapDownloaderTask task =newBitmapDownloaderTask(imageView);
task.execute(url);
}
}
/* class BitmapDownloaderTask, see below */
}
The BitmapDownloaderTask
is the AsyncTask which will actually download the image. It is started using execute
, which returns immediately hence making this method really fast which is the whole purpose since it will be called from the UI thread. Here is the implementation of this class:
classBitmapDownloaderTaskextendsAsyncTask<String,Void,Bitmap>{
privateString url;
privatefinalWeakReference<ImageView> imageViewReference;
publicBitmapDownloaderTask(ImageView imageView){
imageViewReference =newWeakReference<ImageView>(imageView);
}
@Override
// Actual download method, run in the task thread
protectedBitmap doInBackground(String...params){
// params comes from the execute() call: params[0] is the url.
return downloadBitmap(params[0]);
}
@Override
// Once the image is downloaded, associates it to the imageView
protectedvoid onPostExecute(Bitmap bitmap){
if(isCancelled()){
bitmap =null;
}
if(imageViewReference !=null){
ImageView imageView = imageViewReference.get();
if(imageView !=null){
imageView.setImageBitmap(bitmap);
}
}
}
}
The doInBackground
method is the one which is actually run in its own process by the task. It simply uses the downloadBitmap
method we implemented at the beginning of this article.
onPostExecute
is run in the calling UI thread when the task is finished. It takes the resulting Bitmap as a parameter, which is simply associated with the imageView that was provided to download
and was stored in the BitmapDownloaderTask
. Note that this ImageView is stored as a WeakReference
, so that a download in progress does not prevent a killed activity's ImageView from being garbage collected. This explains why we have to check that both the weak reference and the imageView
are not null (i.e. were not collected) before using them in onPostExecute
.
This simplified example illustrates the use on an AsyncTask
, and if you try it, you'll see that these few lines of code actually dramatically improved the performance of the ListView which now scrolls smoothly. Read Painless threading for more details on AsyncTasks.
However, a ListView-specific behavior reveals a problem with our current implementation. Indeed, for memory efficiency reasons, ListView recycles the views that are displayed when the user scrolls. If one flings the list, a given ImageView object will be used many times. Each time it is displayed the ImageView correctly triggers an image download task, which will eventually change its image. So where is the problem? As with most parallel applications, the key issue is in the ordering. In our case, there's no guarantee that the download tasks will finish in the order in which they were started. The result is that the image finally displayed in the list may come from a previous item, which simply happened to have taken longer to download. This is not an issue if the images you download are bound once and for all to given ImageViews, but let's fix it for the common case where they are used in a list.
Handling concurrency
To solve this issue, we should remember the order of the downloads, so that the last started one is the one that will effectively be displayed. It is indeed sufficient for each ImageView to remember its last download. We will add this extra information in the ImageView using a dedicated Drawable subclass, which will be temporarily bind to the ImageView while the download is in progress. Here is the code of our DownloadedDrawable
class:
staticclassDownloadedDrawableextendsColorDrawable{
privatefinalWeakReference<BitmapDownloaderTask> bitmapDownloaderTaskReference;
publicDownloadedDrawable(BitmapDownloaderTask bitmapDownloaderTask){
super(Color.BLACK);
bitmapDownloaderTaskReference =
newWeakReference<BitmapDownloaderTask>(bitmapDownloaderTask);
}
publicBitmapDownloaderTask getBitmapDownloaderTask(){
return bitmapDownloaderTaskReference.get();
}
}
This implementation is backed by a ColorDrawable
, which will result in the ImageView displaying a black background while its download is in progress. One could use a “download in progress” image instead, which would provide feedback to the user. Once again, note the use of a WeakReference to limit object dependencies.
Let's change our code to take this new class into account. First, the download
method will now create an instance of this class and associate it with the imageView:
publicvoid download(String url,ImageView imageView){
if(cancelPotentialDownload(url, imageView)){
BitmapDownloaderTask task =newBitmapDownloaderTask(imageView);
DownloadedDrawable downloadedDrawable =newDownloadedDrawable(task);
imageView.setImageDrawable(downloadedDrawable);
task.execute(url, cookie);
}
}
The cancelPotentialDownload
method will stop the possible download in progress on this imageView since a new one is about to start. Note that this is not sufficient to guarantee that the newest download is always displayed, since the task may be finished, waiting in its onPostExecute
method, which may still may be executed after the one of this new download.
privatestaticboolean cancelPotentialDownload(String url,ImageView imageView){
BitmapDownloaderTask bitmapDownloaderTask = getBitmapDownloaderTask(imageView);
if(bitmapDownloaderTask !=null){
String bitmapUrl = bitmapDownloaderTask.url;
if((bitmapUrl ==null)||(!bitmapUrl.equals(url))){
bitmapDownloaderTask.cancel(true);
}else{
// The same URL is already being downloaded.
returnfalse;
}
}
returntrue;
}
cancelPotentialDownload
uses the cancel
method of the AsyncTask class to stop the download in progress. It returns true
most of the time, so that the download can be started in download
. The only reason we don't want this to happen is when a download is already in progress on the same URL in which case we let it continue. Note that with this implementation, if an ImageView is garbage collected, its associated download is not stopped. A RecyclerListener
might be used for that.
This method uses a helper getBitmapDownloaderTask
function, which is pretty straigthforward:
privatestaticBitmapDownloaderTask getBitmapDownloaderTask(ImageView imageView){
if(imageView !=null){
Drawable drawable = imageView.getDrawable();
if(drawable instanceofDownloadedDrawable){
DownloadedDrawable downloadedDrawable =(DownloadedDrawable)drawable;
return downloadedDrawable.getBitmapDownloaderTask();
}
}
returnnull;
}
Finally, onPostExecute
has to be modified so that it will bind the Bitmap only if this ImageView is still associated with thisdownload process:
if(imageViewReference !=null){
ImageView imageView = imageViewReference.get();
BitmapDownloaderTask bitmapDownloaderTask = getBitmapDownloaderTask(imageView);
// Change bitmap only if this process is still associated with it
if(this== bitmapDownloaderTask){
imageView.setImageBitmap(bitmap);
}
}
With these modifications, our ImageDownloader
class provides the basic services we expect from it. Feel free to use it or the asynchronous pattern it illustrates in your applications to ensure their responsiveness.
Demo
The source code of this article is available online on Google Code. You can switch between and compare the three different implementations that are described in this article (no asynchronous task, no bitmap to task association and the final correct version). Note that the cache size has been limited to 10 images to better demonstrate the issues.
Future work
This code was simplified to focus on its parallel aspects and many useful features are missing from our implementation. TheImageDownloader
class would first clearly benefit from a cache, especially if it is used in conjuction with a ListView, which will probably display the same image many times as the user scrolls back and forth. This can easily be implemented using a Least Recently Used cache backed by a LinkedHashMap
of URL to Bitmap SoftReferences
. More involved cache mechanism could also rely on a local disk storage of the image. Thumbnails creation and image resizing could also be added if needed.
Download errors and time-outs are correctly handled by our implementation, which will return a null
Bitmap in these case. One may want to display an error image instead.
Our HTTP request is pretty simple. One may want to add parameters or cookies to the request as required by certain web sites.
The AsyncTask class used in this article is a really convenient and easy way to defer some work from the UI thread. You may want to use the Handler
class to have a finer control on what you do, such as controlling the total number of download threads which are running in parallel in this case.
[转]Android图片下载的更多相关文章
- picasso_强大的Android图片下载缓存库
tag: android pic skill date: 2016/07/09 title: picasso-强大的Android图片下载缓存库 [本文转载自:泡在网上的日子 参考:http://bl ...
- 毕加索的艺术——Picasso,一个强大的Android图片下载缓存库,OkHttpUtils的使用,二次封装PicassoUtils实现微信精选
毕加索的艺术--Picasso,一个强大的Android图片下载缓存库,OkHttpUtils的使用,二次封装PicassoUtils实现微信精选 官网: http://square.github.i ...
- picasso-强大的Android图片下载缓存库
编辑推荐:稀土掘金,这是一个针对技术开发者的一个应用,你可以在掘金上获取最新最优质的技术干货,不仅仅是Android知识.前端.后端以至于产品和设计都有涉猎,想成为全栈工程师的朋友不要错过! pica ...
- Android图片下载以及缓存框架
实际开发中进行图片下载以及缓存的框架 介绍一下开发中常见图片加载框架的使用和对比一下优缺点. 1.Picasso 框架 在Android中开发,常需要从远程获取图片并显示在客户端,当然我们可以使用原生 ...
- Android图片下载到本地,系统图库不显示
可能大家都知道我们下载图片到Android手机的时候,然后调用系统图库打开图片,提示"找不到指定项". 那是因为我们插入的图片还没有更新的缘故,所以只要将图片插入系统图库,之后发条 ...
- 如何使用picasso 对Android图片下载缓存
相比较其他,picasso的图片缓存更加简单一些,他只需要一行代码就可以表述:导入相关jar包 Picasso.with(context).load("图片路径").into(Im ...
- 具体解说Android图片下载框架UniversialImageLoader之内存缓存(三)
前面的两篇文章着重介绍的是磁盘缓存,这篇文章主要是解说一下内存缓存.对于内存缓存.也打算分两篇文章来进行解说.在这一篇文章中,我们主要是关注三个类, MemoryCache.BaseMemoryCac ...
- Android异步下载图片并且缓存图片到本地
Android异步下载图片并且缓存图片到本地 在Android开发中我们经常有这样的需求,从服务器上下载xml或者JSON类型的数据,其中包括一些图片资源,本demo模拟了这个需求,从网络上加载XML ...
- 【转】Picasso – Android系统的图片下载和缓存类库
来源:http://blog.chengyunfeng.com/?p=492 另一篇参考:http://blog.csdn.net/xu_fu/article/details/17043231 Pic ...
随机推荐
- zzu--2014年11月16日月潭赛 C称号
1230: Magnets Time Limit: 1 Sec Memory Limit: 128 MB Submit: 24 Solved: 13 [id=1230" style=&q ...
- Scrapy研究和探索(五岁以下儿童)——爬行自己主动多页(抢别人博客所有文章)
首先.在教程(二)(http://blog.csdn.net/u012150179/article/details/32911511)中,研究的是爬取单个网页的方法.在教程(三)(http://blo ...
- Android:ViewPager详细解释(异步网络负载图片,有图片缓存,)并与导航点
android 应用.准则欢迎页面. 和图像旋转木马特征, 或者没有很多其他的内容显示在一个页面.以被划分成多个页面,在这一刻viewpager这是非常容易使用. 首先看下效果: 以下是一个样例.带异 ...
- SSH没有password安全日志
client: ssh-keygen -t rsa server结束 mkdir .ssh chmod 755 .ssh 从公开密钥client上传server scp .ssh/id_rsa.phb ...
- 64位WIN7+oracle11g+plsql
64位WIN7+oracle11g+plsql安装 Posted on 2015-07-28 22:41 算命大师不算卦 阅读(27) 评论(0) 编辑 收藏 上部转自Oracle 11g R2 fo ...
- UVA11983 - Weird Advertisement(扫描线)
UVA11983 - Weird Advertisement(扫描线) 题目链接 题目大意:给你n个覆盖矩形,问哪些整数点是被覆盖了k次. 题目大意:这题和hdu1542是一个题型.可是这题求的是覆盖 ...
- hdu2191 悼念512汶川大地震遇难同胞——珍惜如今,感恩生活
转载请注明出处:http://blog.csdn.net/u012860063 题目链接:http://acm.hdu.edu.cn/showproblem.php?pid=2191 Problem ...
- 开发者:网站 & SDK
{ 收集的一些.开发工具 } Teambition 团队协作工具 GitCafe 代码托管 FIR.im App 托管平台 Coding 代码托管,项目管理,WebIDE 计蒜客 编程学习 SendC ...
- jQuery插件编写及链式编程模型
jQuery插件编写及链式编程模型小结 JQuery极大的提高了我们编写JavaScript的效率,让我们可以愉快的编写代码,做出各种特效.大多数情况下,我们都是使用别人开发的JQuery插件,今天我 ...
- 对[foreach]的浅究到发现[yield]
原文:对[foreach]的浅究到发现[yield] 闲来无事,翻了翻以前的代码,做点总结,菜鸟从这里起航,呵呵. 一.List的foreach遍历 先上代码段[1]: class Program { ...