SharedPreferences.Editor 的apply()与commit()方法的区别

最新推荐文章于 2020-03-26 11:06:56 发布

转载最新推荐文章于 2020-03-26 11:06:56 发布 · 50 阅读

0 ·

CC 4.0 BY-SA版权

原文链接：http://www.cnblogs.com/zhaohongtian/p/6808950.html

文章标签：

#移动开发

本文详细对比了Android中SharedPreferences的commit与apply方法。commit方法为同步操作，返回执行结果；而apply为异步操作，直接提交更改到内存并后台写入磁盘，适用于忽略返回值的场景。

commit()的文档

官方文档如下:

Commit your preferences changes back from this Editor to the SharedPreferences object it is editing. This atomically performs the requested modifications, replacing whatever is currently in the SharedPreferences.

Note that when two editors are modifying preferences at the same time, the last one to call commit wins.

If you don't care about the return value and you're using this from your application's main thread, consider using apply() instead.

apply()的文档

官方文档如下:

Note that when two editors are modifying preferences at the same time, the last one to call apply wins.

Unlike commit(), which writes its preferences out to persistent storage synchronously, apply() commits its changes to the in-memory SharedPreferences immediately but starts an asynchronous commit to disk and you won't be notified of any failures. If another editor on this SharedPreferences does a regular commit() while a apply() is still outstanding, the commit() will block until all async commits are completed as well as the commit itself.

As SharedPreferences instances are singletons within a process, it's safe to replace any instance of commit() with apply() if you were already ignoring the return value.

You don't need to worry about Android component lifecycles and their interaction with apply() writing to disk. The framework makes sure in-flight disk writes from apply() complete before switching states.

解释说明

需要注意的是commit()方法是Added in API level 1的,也就是sdk1就已经存在了.
apply()方法是Added in API level 9的.
commit()有返回值,成功返回true,失败返回false.commit()方法是同步提交到硬件磁盘，因此，在多个并发的提交commit的时候，他们会等待正在处理的commit保存到磁盘后在操作，从而降低了效率。
apply()没有返回值.apply()是将修改的数据提交到内存, 而后异步真正的提交到硬件磁盘.