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閱讀 228,345評論 6 531
  • 序言:濱河連續發生了三起死亡事件,死亡現場離奇詭異,居然都是意外死亡,警方通過查閱死者的電腦和手機,發現死者居然都...
    沈念sama閱讀 98,494評論 3 416
  • 文/潘曉璐 我一進店門,熙熙樓的掌柜王于貴愁眉苦臉地迎上來,“玉大人,你說我怎么就攤上這事。” “怎么了?”我有些...
    開封第一講書人閱讀 176,283評論 0 374
  • 文/不壞的土叔 我叫張陵,是天一觀的道長。 經常有香客問我,道長,這世上最難降的妖魔是什么? 我笑而不...
    開封第一講書人閱讀 62,953評論 1 309
  • 正文 為了忘掉前任,我火速辦了婚禮,結果婚禮上,老公的妹妹穿的比我還像新娘。我一直安慰自己,他們只是感情好,可當我...
    茶點故事閱讀 71,714評論 6 410
  • 文/花漫 我一把揭開白布。 她就那樣靜靜地躺著,像睡著了一般。 火紅的嫁衣襯著肌膚如雪。 梳的紋絲不亂的頭發上,一...
    開封第一講書人閱讀 55,186評論 1 324
  • 那天,我揣著相機與錄音,去河邊找鬼。 笑死,一個胖子當著我的面吹牛,可吹牛的內容都是我干的。 我是一名探鬼主播,決...
    沈念sama閱讀 43,255評論 3 441
  • 文/蒼蘭香墨 我猛地睜開眼,長吁一口氣:“原來是場噩夢啊……” “哼!你這毒婦竟也來了?” 一聲冷哼從身側響起,我...
    開封第一講書人閱讀 42,410評論 0 288
  • 序言:老撾萬榮一對情侶失蹤,失蹤者是張志新(化名)和其女友劉穎,沒想到半個月后,有當地人在樹林里發現了一具尸體,經...
    沈念sama閱讀 48,940評論 1 335
  • 正文 獨居荒郊野嶺守林人離奇死亡,尸身上長有42處帶血的膿包…… 初始之章·張勛 以下內容為張勛視角 年9月15日...
    茶點故事閱讀 40,776評論 3 354
  • 正文 我和宋清朗相戀三年,在試婚紗的時候發現自己被綠了。 大學時的朋友給我發了我未婚夫和他白月光在一起吃飯的照片。...
    茶點故事閱讀 42,976評論 1 369
  • 序言:一個原本活蹦亂跳的男人離奇死亡,死狀恐怖,靈堂內的尸體忽然破棺而出,到底是詐尸還是另有隱情,我是刑警寧澤,帶...
    沈念sama閱讀 38,518評論 5 359
  • 正文 年R本政府宣布,位于F島的核電站,受9級特大地震影響,放射性物質發生泄漏。R本人自食惡果不足惜,卻給世界環境...
    茶點故事閱讀 44,210評論 3 347
  • 文/蒙蒙 一、第九天 我趴在偏房一處隱蔽的房頂上張望。 院中可真熱鬧,春花似錦、人聲如沸。這莊子的主人今日做“春日...
    開封第一講書人閱讀 34,642評論 0 26
  • 文/蒼蘭香墨 我抬頭看了看天上的太陽。三九已至,卻和暖如春,著一層夾襖步出監牢的瞬間,已是汗流浹背。 一陣腳步聲響...
    開封第一講書人閱讀 35,878評論 1 286
  • 我被黑心中介騙來泰國打工, 沒想到剛下飛機就差點兒被人妖公主榨干…… 1. 我叫王不留,地道東北人。 一個月前我還...
    沈念sama閱讀 51,654評論 3 391
  • 正文 我出身青樓,卻偏偏與公主長得像,于是被迫代替她去往敵國和親。 傳聞我的和親對象是個殘疾皇子,可洞房花燭夜當晚...
    茶點故事閱讀 47,958評論 2 373

推薦閱讀更多精彩內容