android同步操作框架

关键组件:

ContentResolver

ContentService

SyncManager

SyncManager.ActiveSyncContext

SyncManager.SyncOperation

SyncManager.SyncHandler

ContentResolver

外部的应用程序通过调用ContentResolve.requestSync()静态方法发起同步:

[java]

/**

* @param account which account should be synced

* @param authority which authority should be synced

* @param extras any extras to pass to the SyncAdapter.

*/

public static void requestSync(Account account, String authority, Bundle extras) {

validateSyncExtrasBundle(extras);

try {

getContentService().requestSync(account, authority, extras);

} catch (RemoteException e) {

}

}

/**

* @param account which account should be synced

* @param authority which authority should be synced

* @param extras any extras to pass to the SyncAdapter.

*/

public static void requestSync(Account account, String authority, Bundle extras) {

validateSyncExtrasBundle(extras);

try {

getContentService().requestSync(account, authority, extras);

} catch (RemoteException e) {

}

}

方法接收三个参数:

- account:需要同步的帐号

- authority:需要进行同步的authority

- extras:需要传递给sync adapter的附加数据

在这里,getContentService()方法返回系统服务ContentService的代理对象,然后通过它远程调用ContentService.requestSync()。

ContentService

ContentService是Android系统服务,它提供一系列数据同步及数据访问等相关的操作。它的行为在IContentService.aidl中描述。

这里,通过远程调用ContentService.requestSync()方法来启动针对指定帐号(account)的指定内容(authority)的同步:

[java]

public void requestSync(Account account, String authority, Bundle extras) {

...

try {

SyncManager syncManager = getSyncManager();

if (syncManager != null) {

syncManager.scheduleSync(account, userId, authority, extras, 0 /* no delay */,

false /* onlyThoseWithUnkownSyncableState */);

}

}

...

}

public void requestSync(Account account, String authority, Bundle extras) {

...

try {

SyncManager syncManager = getSyncManager();

if (syncManager != null) {

syncManager.scheduleSync(account, userId, authority, extras, 0 /* no delay */,

false /* onlyThoseWithUnkownSyncableState */);

}

}

...

}

在这个方法中,会获取一个SyncManager类的实例。顾名思义,SyncManager管理与同步相关的处理。

SyncManager

[java]

public void scheduleSync(Account requestedAccount, int userId, String requestedAuthority,

Bundle extras, long delay, boolean onlyThoseWithUnkownSyncableState) {

...

final boolean backgroundDataUsageAllowed = !mBootCompleted ||

getConnectivityManager().getBackgroundDataSetting();

...

// 产生一个同步帐户列表。对于手动同步,列表中仅有一个AccountUser元素,它封装了需要同步的帐号以及对应的应用程序(userId)

AccountAndUser[] accounts;

if (requestedAccount != null && userId != UserHandle.USER_ALL) {

accounts = new AccountAndUser[] { new AccountAndUser(requestedAccount, userId) };

}

...

for (AccountAndUser account : accounts) {

// 在这里,会扫描系统中所有提供了sync adapter的service:根据intent filter

// 然后从得到service info中取得各自的authority。service info从对应服务的meta-data标签中指定的sync adapter描述文件中解析出来。

final HashSet syncableAuthorities = new HashSet();

for (RegisteredServicesCache.ServiceInfo syncAdapter :

mSyncAdapters.getAllServices(account.userId)) {

syncableAuthorities.add(syncAdapter.type.authority);

}

...

for (String authority : syncableAuthorities) {

// 检查帐户是否能够同步

int isSyncable = mSyncStorageEngine.getIsSyncable(account.account, account.userId,

authority);

if (isSyncable == 0) {

continue;

}

final RegisteredServicesCache.ServiceInfo syncAdapterInfo;

syncAdapterInfo = mSyncAdapters.getServiceInfo(

SyncAdapterType.newKey(authority, account.account.type), account.userId);

...

if (isSyncable < 0) {

Bundle newExtras = new Bundle();

newExtras.putBoolean(ContentResolver.SYNC_EXTRAS_INITIALIZE, true);

...

// 部署同步操作

scheduleSyncOperation(

new SyncOperation(account.account, account.userId, source, authority,

newExtras, 0, backoffTime, delayUntil, allowParallelSyncs));

}

...

}

}

}

public void scheduleSync(Account requestedAccount, int userId, String requestedAuthority,

Bundle extras, long delay, boolean onlyThoseWithUnkownSyncableState) {

...

final boolean backgroundDataUsageAllowed = !mBootCompleted ||

getConnectivityManager().getBackgroundDataSetting();

...

// 产生一个同步帐户列表。对于手动同步,列表中仅有一个AccountUser元素,它封装了需要同步的帐号以及对应的应用程序(userId)

AccountAndUser[] accounts;

if (requestedAccount != null && userId != UserHandle.USER_ALL) {

accounts = new AccountAndUser[] { new AccountAndUser(requestedAccount, userId) };

}

...

for (AccountAndUser account : accounts) {

// 在这里,会扫描系统中所有提供了sync adapter的service:根据intent filter

// 然后从得到service info中取得各自的authority。service info从对应服务的meta-data标签中指定的sync adapter描述文件中解析出来。

final HashSet syncableAuthorities = new HashSet();

for (RegisteredServicesCache.ServiceInfo syncAdapter :

mSyncAdapters.getAllServices(account.userId)) {

syncableAuthorities.add(syncAdapter.type.authority);

}

...

for (String authority : syncableAuthorities) {

// 检查帐户是否能够同步

int isSyncable = mSyncStorageEngine.getIsSyncable(account.account, account.userId,

authority);

if (isSyncable == 0) {

continue;

}

final RegisteredServicesCache.ServiceInfo syncAdapterInfo;

syncAdapterInfo = mSyncAdapters.getServiceInfo(

SyncAdapterType.newKey(authority, account.account.type), account.userId);

...

if (isSyncable < 0) {

Bundle newExtras = new Bundle();

newExtras.putBoolean(ContentResolver.SYNC_EXTRAS_INITIALIZE, true);

...

// 部署同步操作

scheduleSyncOperation(

new SyncOperation(account.account, account.userId, source, authority,

newExtras, 0, backoffTime, delayUntil, allowParallelSyncs));

}

...

}

}

}

这里,首先从系统中筛选出符合限定条件的service的信息,然后发起对应的同步。

首先为每一个同步操作生成一个SyncOperation实例,它封装了同步操作需要的全部信息:

[java]

public class SyncOperation implements Comparable {

public final Account account;

public final int userId;

public int syncSource;

public String authority;

public final boolean allowParallelSyncs;

public Bundle extras;

public final String key;

public long earliestRunTime;

public boolean expedited;

public SyncStorageEngine.PendingOperation pendingOperation;

public Long backoff;

public long delayUntil;

public long effectiveRunTime;

public class SyncOperation implements Comparable {

public final Account account;

public final int userId;

public int syncSource;

public String authority;

public final boolean allowParallelSyncs;

public Bundle extras;

public final String key;

public long earliestRunTime;

public boolean expedited;

public SyncStorageEngine.PendingOperation pendingOperation;

public Long backoff;

public long delayUntil;

public long effectiveRunTime;

然后调用scheduleSyncOperation方法:

[java]

public void scheduleSyncOperation(SyncOperation syncOperation) {

boolean queueChanged;

synchronized (mSyncQueue) {

queueChanged = mSyncQueue.add(syncOperation);

}

if (queueChanged) {

...

sendCheckAlarmsMessage();

}

...

}

public void scheduleSyncOperation(SyncOperation syncOperation) {

boolean queueChanged;

synchronized (mSyncQueue) {

queueChanged = mSyncQueue.add(syncOperation);

}

if (queueChanged) {

...

sendCheckAlarmsMessage();

}

...

}

首先将SyncOperation实例插入队列mSyncQueue然后向SyncManager中定义的SyncHandler发送消息,通知其队列发生变化:

[java]

private void sendCheckAlarmsMessage() {

...

mSyncHandler.removeMessages(SyncHandler.MESSAGE_CHECK_ALARMS);

mSyncHandler.sendEmptyMessage(SyncHandler.MESSAGE_CHECK_ALARMS);

}

private void sendCheckAlarmsMessage() {

...

mSyncHandler.removeMessages(SyncHandler.MESSAGE_CHECK_ALARMS);

mSyncHandler.sendEmptyMessage(SyncHandler.MESSAGE_CHECK_ALARMS);

}

随后,SyncHandler处理这个消息:

[java] v

public void handleMessage(Message msg) {

...

try {

...

switch (msg.what) {

...

case SyncHandler.MESSAGE_CHECK_ALARMS:

...

nextPendingSyncTime = maybeStartNextSyncLocked();

break;

}

}

...

}

public void handleMessage(Message msg) {

...

try {

...

switch (msg.what) {

...

case SyncHandler.MESSAGE_CHECK_ALARMS:

...

nextPendingSyncTime = maybeStartNextSyncLocked();

break;

}

}

...

}

这里,maybeStartNextSyncLocked()方法经过一系列的检查,确认执行同步的全部条件已经达到之后,对SyncOperation进行分发:

[java]

private long maybeStartNextSyncLocked() {

...

dispatchSyncOperation(candidate);

}

return nextReadyToRunTime;

}

private long maybeStartNextSyncLocked() {

...

dispatchSyncOperation(candidate);

}

return nextReadyToRunTime;

}

接下来,将绑定到提供sync adapter的应用程序中对应的service:

[java]

private boolean dispatchSyncOperation(SyncOperation op) {

...

// connect to the sync adapter

SyncAdapterType syncAdapterType = SyncAdapterType.newKey(op.authority, op.account.type);

final RegisteredServicesCache.ServiceInfo syncAdapterInfo;

syncAdapterInfo = mSyncAdapters.getServiceInfo(syncAdapterType, op.userId);

...

ActiveSyncContext activeSyncContext =

new ActiveSyncContext(op, insertStartSyncEvent(op), syncAdapterInfo.uid);

activeSyncContext.mSyncInfo = mSyncStorageEngine.addActiveSync(activeSyncContext);

mActiveSyncContexts.add(activeSyncContext);

...

if (!activeSyncContext.bindToSyncAdapter(syncAdapterInfo, op.userId)) {

Log.e(TAG, "Bind attempt failed to " + syncAdapterInfo);

closeActiveSyncContext(activeSyncContext);

return false;

}

return true;

}

private boolean dispatchSyncOperation(SyncOperation op) {

...

// connect to the sync adapter

SyncAdapterType syncAdapterType = SyncAdapterType.newKey(op.authority, op.account.type);

final RegisteredServicesCache.ServiceInfo syncAdapterInfo;

syncAdapterInfo = mSyncAdapters.getServiceInfo(syncAdapterType, op.userId);

...

ActiveSyncContext activeSyncContext =

new ActiveSyncContext(op, insertStartSyncEvent(op), syncAdapterInfo.uid);

activeSyncContext.mSyncInfo = mSyncStorageEngine.addActiveSync(activeSyncContext);

mActiveSyncContexts.add(activeSyncContext);

...

if (!activeSyncContext.bindToSyncAdapter(syncAdapterInfo, op.userId)) {

Log.e(TAG, "Bind attempt failed to " + syncAdapterInfo);

closeActiveSyncContext(activeSyncContext);

return false;

}

return true;

}

与前面的AccountManager非常的雷同,这里通过ActiveSyncContext类来完成service的绑定:

[java]

class ActiveSyncContext extends ISyncContext.Stub

implements ServiceConnection, IBinder.DeathRecipient {

...

public void onServiceConnected(ComponentName name, IBinder service) {

Message msg = mSyncHandler.obtainMessage();

msg.what = SyncHandler.MESSAGE_SERVICE_CONNECTED;

msg.obj = new ServiceConnectionData(this, ISyncAdapter.Stub.asInterface(service));

mSyncHandler.sendMessage(msg);

}

...

boolean bindToSyncAdapter(RegisteredServicesCache.ServiceInfo info, int userId) {

if (Log.isLoggable(TAG, Log.VERBOSE)) {

Log.d(TAG, "bindToSyncAdapter: " + info.componentName + ", connection " + this);

}

Intent intent = new Intent();

intent.setAction("android.content.SyncAdapter");

intent.setComponent(info.componentName);

intent.putExtra(Intent.EXTRA_CLIENT_LABEL,

com.android.internal.R.string.sync_binding_label);

intent.putExtra(Intent.EXTRA_CLIENT_INTENT, PendingIntent.getActivityAsUser(

mContext, 0, new Intent(Settings.ACTION_SYNC_SETTINGS), 0,

null, new UserHandle(userId)));

mBound = true;

final boolean bindResult = mContext.bindService(intent, this,

Context.BIND_AUTO_CREATE | Context.BIND_NOT_FOREGROUND

| Context.BIND_ALLOW_OOM_MANAGEMENT,

mSyncOperation.userId);

if (!bindResult) {

mBound = false;

}

return bindResult;

}

...

}

class ActiveSyncContext extends ISyncContext.Stub

implements ServiceConnection, IBinder.DeathRecipient {

...

public void onServiceConnected(ComponentName name, IBinder service) {

Message msg = mSyncHandler.obtainMessage();

msg.what = SyncHandler.MESSAGE_SERVICE_CONNECTED;

msg.obj = new ServiceConnectionData(this, ISyncAdapter.Stub.asInterface(service));

mSyncHandler.sendMessage(msg);

}

...

boolean bindToSyncAdapter(RegisteredServicesCache.ServiceInfo info, int userId) {

if (Log.isLoggable(TAG, Log.VERBOSE)) {

Log.d(TAG, "bindToSyncAdapter: " + info.componentName + ", connection " + this);

}

Intent intent = new Intent();

intent.setAction("android.content.SyncAdapter");

intent.setComponent(info.componentName);

intent.putExtra(Intent.EXTRA_CLIENT_LABEL,

com.android.internal.R.string.sync_binding_label);

intent.putExtra(Intent.EXTRA_CLIENT_INTENT, PendingIntent.getActivityAsUser(

mContext, 0, new Intent(Settings.ACTION_SYNC_SETTINGS), 0,

null, new UserHandle(userId)));

mBound = true;

final boolean bindResult = mContext.bindService(intent, this,

Context.BIND_AUTO_CREATE | Context.BIND_NOT_FOREGROUND

| Context.BIND_ALLOW_OOM_MANAGEMENT,

mSyncOperation.userId);

if (!bindResult) {

mBound = false;

}

return bindResult;

}

...

}其中,bindToSyncAdapter()中创建相应的Intent,发起绑定。

然后,因为本类实现了ServiceConnection接口,所以当绑定成功时,将回调本类的onServiceConnected()方法。在这个回调中,向SyncHandler发送一条MESSAGE_SERVICE_CONNECTED消息。

紧接着,轮到SyncHandler来处理消息:

case SyncHandler.MESSAGE_SERVICE_CONNECTED: {

ServiceConnectionData msgData = (ServiceConnectionData)msg.obj;

if (Log.isLoggable(TAG, Log.VERBOSE)) {

Log.d(TAG, "handleSyncHandlerMessage: MESSAGE_SERVICE_CONNECTED: "

+ msgData.activeSyncContext);

}

// check that this isn't an old message

if (isSyncStillActive(msgData.activeSyncContext)) {

runBoundToSyncAdapter(msgData.activeSyncContext, msgData.syncAdapter);

}

break;

}

case SyncHandler.MESSAGE_SERVICE_CONNECTED: {

ServiceConnectionData msgData = (ServiceConnectionData)msg.obj;

if (Log.isLoggable(TAG, Log.VERBOSE)) {

Log.d(TAG, "handleSyncHandlerMessage: MESSAGE_SERVICE_CONNECTED: "

+ msgData.activeSyncContext);

}

// check that this isn't an old message

if (isSyncStillActive(msgData.activeSyncContext)) {

runBoundToSyncAdapter(msgData.activeSyncContext, msgData.syncAdapter);

}

break;

}

这里主要就是调用了runBoundToSyncAdapter()方法:

[java]

private void runBoundToSyncAdapter(final ActiveSyncContext activeSyncContext,

ISyncAdapter syncAdapter) {

activeSyncContext.mSyncAdapter = syncAdapter;

final SyncOperation syncOperation = activeSyncContext.mSyncOperation;

try {

...

syncAdapter.startSync(activeSyncContext, syncOperation.authority,

syncOperation.account, syncOperation.extras);

}

...

}

最后编辑于
©著作权归作者所有,转载或内容合作请联系作者
  • 序言:七十年代末,一起剥皮案震惊了整个滨河市,随后出现的几起案子,更是在滨河造成了极大的恐慌,老刑警刘岩,带你破解...
    沈念sama阅读 203,324评论 5 476
  • 序言:滨河连续发生了三起死亡事件,死亡现场离奇诡异,居然都是意外死亡,警方通过查阅死者的电脑和手机,发现死者居然都...
    沈念sama阅读 85,303评论 2 381
  • 文/潘晓璐 我一进店门,熙熙楼的掌柜王于贵愁眉苦脸地迎上来,“玉大人,你说我怎么就摊上这事。” “怎么了?”我有些...
    开封第一讲书人阅读 150,192评论 0 337
  • 文/不坏的土叔 我叫张陵,是天一观的道长。 经常有香客问我,道长,这世上最难降的妖魔是什么? 我笑而不...
    开封第一讲书人阅读 54,555评论 1 273
  • 正文 为了忘掉前任,我火速办了婚礼,结果婚礼上,老公的妹妹穿的比我还像新娘。我一直安慰自己,他们只是感情好,可当我...
    茶点故事阅读 63,569评论 5 365
  • 文/花漫 我一把揭开白布。 她就那样静静地躺着,像睡着了一般。 火红的嫁衣衬着肌肤如雪。 梳的纹丝不乱的头发上,一...
    开封第一讲书人阅读 48,566评论 1 281
  • 那天,我揣着相机与录音,去河边找鬼。 笑死,一个胖子当着我的面吹牛,可吹牛的内容都是我干的。 我是一名探鬼主播,决...
    沈念sama阅读 37,927评论 3 395
  • 文/苍兰香墨 我猛地睁开眼,长吁一口气:“原来是场噩梦啊……” “哼!你这毒妇竟也来了?” 一声冷哼从身侧响起,我...
    开封第一讲书人阅读 36,583评论 0 257
  • 序言:老挝万荣一对情侣失踪,失踪者是张志新(化名)和其女友刘颖,没想到半个月后,有当地人在树林里发现了一具尸体,经...
    沈念sama阅读 40,827评论 1 297
  • 正文 独居荒郊野岭守林人离奇死亡,尸身上长有42处带血的脓包…… 初始之章·张勋 以下内容为张勋视角 年9月15日...
    茶点故事阅读 35,590评论 2 320
  • 正文 我和宋清朗相恋三年,在试婚纱的时候发现自己被绿了。 大学时的朋友给我发了我未婚夫和他白月光在一起吃饭的照片。...
    茶点故事阅读 37,669评论 1 329
  • 序言:一个原本活蹦乱跳的男人离奇死亡,死状恐怖,灵堂内的尸体忽然破棺而出,到底是诈尸还是另有隐情,我是刑警宁泽,带...
    沈念sama阅读 33,365评论 4 318
  • 正文 年R本政府宣布,位于F岛的核电站,受9级特大地震影响,放射性物质发生泄漏。R本人自食恶果不足惜,却给世界环境...
    茶点故事阅读 38,941评论 3 307
  • 文/蒙蒙 一、第九天 我趴在偏房一处隐蔽的房顶上张望。 院中可真热闹,春花似锦、人声如沸。这庄子的主人今日做“春日...
    开封第一讲书人阅读 29,928评论 0 19
  • 文/苍兰香墨 我抬头看了看天上的太阳。三九已至,却和暖如春,着一层夹袄步出监牢的瞬间,已是汗流浃背。 一阵脚步声响...
    开封第一讲书人阅读 31,159评论 1 259
  • 我被黑心中介骗来泰国打工, 没想到刚下飞机就差点儿被人妖公主榨干…… 1. 我叫王不留,地道东北人。 一个月前我还...
    沈念sama阅读 42,880评论 2 349
  • 正文 我出身青楼,却偏偏与公主长得像,于是被迫代替她去往敌国和亲。 传闻我的和亲对象是个残疾皇子,可洞房花烛夜当晚...
    茶点故事阅读 42,399评论 2 342

推荐阅读更多精彩内容