在处理 AsyncTask 和屏幕旋转时，我仍在尝试找到“正确”的设计模式。我阅读了 这篇 Commonsware 博客文章，其中链接到 <一个href="https://github.com/commonsguy/cw-android/blob/master/Rotation/RotationAsync/src/com/commonsware/android/rotation/async/RotationAsync.java" rel="nofollow noreferrer">此代码，但是 onRetainNonConfigurationInstance 方法现已弃用。文档中的神奇句子指出“在切换到下一个活动期间保证不进行消息处理简化了活动对象的使用......”这是该方法所做的真正关键的部分。我没有看到它使用 setRetainInstance() 的建议 能够实现相同的目标。
我还看到了帖子比如这个，其排名第一的答案这实际上是一个糟糕的黑客攻击，它只覆盖了 90% 的用例（即，如果您的任务正在运行，然后接到电话，该解决方案将不起作用，会发生什么情况）。
建议查看此处的代码对于 AsyncTask 示例，但除非我很密集，否则我看不到它们在应用程序中的任何地方使用（当使用 搜索功能在谷歌代码上）
这个问题显然已经被问过很多次了，但我还没有看到最新的、正确的答案。如果存在，请回答并关闭重复（如果必须），但至少回答！ :)
这是另一个链接< /a> 审查相同的、已弃用的方法。
I am still trying to find the "correct" design pattern when dealing with AsyncTasks and screen rotation. I read this commonsware blog post which links to this code, but the onRetainNonConfigurationInstance method is now deprecated. The magic sentence in the documentation states "The guarantee of no message handling during the switch to the next activity simplifies use with active objects..." which is a truly critical part about what this method did. I don't see its suggestion of using setRetainInstance() being able to accomplish the same goal.
I also saw posts such as this one whose number one answer is really nothing short of a bad hack which only covers 90% of use cases (ie. what happens if your task is running and then a phone call comes in, that solution will not work).
It was suggested to review the code here for AsyncTask examples but unless I am being dense, I don't see them being used anywhere in the application (when using the search feature on google code)
This question has obviously been asked many times but I have not seen an up to date, proper asnwer. If one exists, please answer and close as duplicate if you must, but at least answer! :)
This is another link which reviews the same, deprecated method.
发布评论
评论（2）
它仅在 Honeycomb 及更高版本上被弃用，并且它在这些上也可以正常工作。 “新”方法是使用加载器（您可以使用兼容性库来获取 HC 之前版本中的加载器）或保留片段。如果您调用
setRetainInstance()实例将按原样传递给新创建的 Activity（它们实际上在兼容性库的FragmentActivity中使用onRetainNonConfigurationInstance） ，所以它实际上与您现在拥有的相同。It's only deprecated on Honeycomb and above, and it will work just fine on those too. The 'new' way is to use loaders (you can use the compatibility library to get those in pre-HC versions) or retained fragments. If you call
setRetainInstance()the instance passed as is to the newly created activity (they actually useonRetainNonConfigurationInstancein theFragmentActivityof the compatibility library), so it's effectively the same as what you have now.使用已弃用的方法本身并没有什么问题。如果您的 AsyncTask 非常重要，以至于您无法在方向改变时取消它并重新启动它，那么您应该考虑使用服务。
There's nothing inherently wrong with using a deprecated method. If your AsyncTask is THAT critical that you can't cancel it and start it up again if your orientation changes, you should consider using a service.