基于Andoird 4.2.2的同步框架源代碼學(xué)習(xí)——同步發(fā)起端




關(guān)鍵組件：
ContentResolver
ContentService
SyncManager
SyncManager.ActiveSyncContext
SyncManager.SyncOperation
SyncManager.SyncHandler
ContentResolver
外部的應(yīng)用程序通過調(diào)用ContentResolve.requestSync()靜態(tài)方法發(fā)起同步：



[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) {
??????? }
??? }
方法接收三個(gè)參數(shù)：


- account：需要同步的帳號


- authority：需要進(jìn)行同步的authority


- extras：需要傳遞給sync adapter的附加數(shù)據(jù)


在這里，getContentService()方法返回系統(tǒng)服務(wù)ContentService的代理對象，然后通過它遠(yuǎn)程調(diào)用ContentService.requestSync()。





ContentService
ContentService是Android的系統(tǒng)服務(wù)裁替，它提供一系列數(shù)據(jù)同步及數(shù)據(jù)訪問等相關(guān)的操作朴恳。它的行為在IContentService.aidl中描述瞄勾。


這里帕胆，通過遠(yuǎn)程調(diào)用ContentService.requestSync()方法來啟動(dòng)針對指定帳號（account）的指定內(nèi)容（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 */);
??????????? }
??????? }
??????? ...
??? }
在這個(gè)方法中，會(huì)獲取一個(gè)SyncManager類的實(shí)例鹤盒。顧名思義，SyncManager管理與同步相關(guān)的處理侦副。





SyncManager


[java]
public void scheduleSync(Account requestedAccount, int userId, String requestedAuthority,?
??????? Bundle extras, long delay, boolean onlyThoseWithUnkownSyncableState) {?
??? ...?
??? final boolean backgroundDataUsageAllowed = !mBootCompleted ||?
??????????? getConnectivityManager().getBackgroundDataSetting();?
??? ...?
?????
??? // 產(chǎn)生一個(gè)同步帳戶列表昨悼。對于手動(dòng)同步，列表中僅有一個(gè)AccountUser元素跃洛，它封裝了需要同步的帳號以及對應(yīng)的應(yīng)用程序（userId）??
??? AccountAndUser[] accounts;?
??? if (requestedAccount != null && userId != UserHandle.USER_ALL) {?
??????? accounts = new AccountAndUser[] { new AccountAndUser(requestedAccount, userId) };?
??? }?
??? ...?
??? for (AccountAndUser account : accounts) {?
??????? // 在這里率触，會(huì)掃描系統(tǒng)中所有提供了sync adapter的service：根據(jù)intent filter??
??????? // 然后從得到service info中取得各自的authority。service info從對應(yīng)服務(wù)的meta-data標(biāo)簽中指定的sync adapter描述文件中解析出來汇竭。??
??????? final HashSet<String> syncableAuthorities = new HashSet<String>();?
??????? for (RegisteredServicesCache.ServiceInfo<SyncAdapterType> 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<SyncAdapterType> 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();
??????? ...
???????
??????? // 產(chǎn)生一個(gè)同步帳戶列表葱蝗。對于手動(dòng)同步，列表中僅有一個(gè)AccountUser元素细燎，它封裝了需要同步的帳號以及對應(yīng)的應(yīng)用程序（userId）
??????? AccountAndUser[] accounts;
??????? if (requestedAccount != null && userId != UserHandle.USER_ALL) {
??????????? accounts = new AccountAndUser[] { new AccountAndUser(requestedAccount, userId) };
??????? }
??????? ...
??????? for (AccountAndUser account : accounts) {
??????????? // 在這里两曼，會(huì)掃描系統(tǒng)中所有提供了sync adapter的service：根據(jù)intent filter
??????????? // 然后從得到service info中取得各自的authority。service info從對應(yīng)服務(wù)的meta-data標(biāo)簽中指定的sync adapter描述文件中解析出來玻驻。
??????????? final HashSet<String> syncableAuthorities = new HashSet<String>();
??????????? for (RegisteredServicesCache.ServiceInfo<SyncAdapterType> 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<SyncAdapterType> 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));
??????????????? }
??????????????? ...
??????????? }
??????? }
??? }
這里悼凑，首先從系統(tǒng)中篩選出符合限定條件的service的信息，然后發(fā)起對應(yīng)的同步璧瞬。


首先為每一個(gè)同步操作生成一個(gè)SyncOperation實(shí)例户辫，它封裝了同步操作需要的全部信息：



[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;
然后調(diào)用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實(shí)例插入隊(duì)列mSyncQueue然后向SyncManager中定義的SyncHandler發(fā)送消息，通知其隊(duì)列發(fā)生變化：



[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處理這個(gè)消息：



[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()方法經(jīng)過一系列的檢查，確認(rèn)執(zhí)行同步的全部條件已經(jīng)達(dá)到之后瘟忱，對SyncOperation進(jìn)行分發(fā)：



[java]
private long maybeStartNextSyncLocked() {?
??????? ...?
??????? dispatchSyncOperation(candidate);?
??? }?
?
??? return nextReadyToRunTime;?
}?


??????? private long maybeStartNextSyncLocked() {
??????????????? ...
??????????????? dispatchSyncOperation(candidate);
??????????? }


??????????? return nextReadyToRunTime;
??????? }
接下來奥额，將綁定到提供sync adapter的應(yīng)用程序中對應(yīng)的service：


[java]
private boolean dispatchSyncOperation(SyncOperation op) {?
??? ...?
??? // connect to the sync adapter??
??? SyncAdapterType syncAdapterType = SyncAdapterType.newKey(op.authority, op.account.type);?
??? final RegisteredServicesCache.ServiceInfo<SyncAdapterType> 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<SyncAdapterType> 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()中創(chuàng)建相應(yīng)的Intent垫挨，發(fā)起綁定。


然后触菜，因?yàn)楸绢悓?shí)現(xiàn)了ServiceConnection接口九榔，所以當(dāng)綁定成功時(shí)，將回調(diào)本類的onServiceConnected()方法。在這個(gè)回調(diào)中帚屉，向SyncHandler發(fā)送一條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;
??????????????????? }
這里主要就是調(diào)用了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);?
??? }?
??? ...?
}?

最后編輯于 ：
?著作權(quán)歸作者所有,轉(zhuǎn)載或內(nèi)容合作請聯(lián)系作者
  • 人面猴
    序言：七十年代末攻旦，一起剝皮案震驚了整個(gè)濱河市喻旷，隨后出現(xiàn)的幾起案子，更是在濱河造成了極大的恐慌牢屋，老刑警劉巖且预，帶你破解...
    沈念sama閱讀 222,681評論 6贊 517
  • 死咒
    序言：濱河連續(xù)發(fā)生了三起死亡事件，死亡現(xiàn)場離奇詭異烙无，居然都是意外死亡锋谐，警方通過查閱死者的電腦和手機(jī)，發(fā)現(xiàn)死者居然都...
    沈念sama閱讀 95,205評論 3贊 399
  • 救了他兩次的神仙讓他今天三更去死
    文/潘曉璐 我一進(jìn)店門截酷，熙熙樓的掌柜王于貴愁眉苦臉地迎上來涮拗，“玉大人，你說我怎么就攤上這事迂苛∪龋” “怎么了？”我有些...
    開封第一講書人閱讀 169,421評論 0贊 362
  • 道士緝兇錄：失蹤的賣姜人
    文/不壞的土叔 我叫張陵三幻，是天一觀的道長就漾。 經(jīng)常有香客問我，道長念搬，這世上最難降的妖魔是什么抑堡？ 我笑而不...
    開封第一講書人閱讀 60,114評論 1贊 300
  • ?港島之戀（遺憾婚禮）
    正文 為了忘掉前任，我火速辦了婚禮朗徊，結(jié)果婚禮上首妖，老公的妹妹穿的比我還像新娘。我一直安慰自己荣倾，他們只是感情好悯搔，可當(dāng)我...
    茶點(diǎn)故事閱讀 69,116評論 6贊 398
  • 惡毒庶女頂嫁案：這布局不是一般人想出來的
    文/花漫 我一把揭開白布。 她就那樣靜靜地躺著舌仍，像睡著了一般。 火紅的嫁衣襯著肌膚如雪通危。 梳的紋絲不亂的頭發(fā)上铸豁，一...
    開封第一講書人閱讀 52,713評論 1贊 312
  • 城市分裂傳說
    那天，我揣著相機(jī)與錄音菊碟，去河邊找鬼节芥。 笑死，一個(gè)胖子當(dāng)著我的面吹牛，可吹牛的內(nèi)容都是我干的头镊。 我是一名探鬼主播蚣驼，決...
    沈念sama閱讀 41,170評論 3贊 422
  • 雙鴛鴦連環(huán)套：你想象不到人心有多黑
    文/蒼蘭香墨 我猛地睜開眼，長吁一口氣：“原來是場噩夢啊……” “哼相艇！你這毒婦竟也來了颖杏？” 一聲冷哼從身側(cè)響起，我...
    開封第一講書人閱讀 40,116評論 0贊 277
  • 萬榮殺人案實(shí)錄
    序言：老撾萬榮一對情侶失蹤坛芽，失蹤者是張志新（化名）和其女友劉穎留储，沒想到半個(gè)月后，有當(dāng)?shù)厝嗽跇淞掷锇l(fā)現(xiàn)了一具尸體咙轩，經(jīng)...
    沈念sama閱讀 46,651評論 1贊 320
  • ?護(hù)林員之死
    正文 獨(dú)居荒郊野嶺守林人離奇死亡获讳，尸身上長有42處帶血的膿包…… 初始之章·張勛 以下內(nèi)容為張勛視角 年9月15日...
    茶點(diǎn)故事閱讀 38,714評論 3贊 342
  • ?白月光啟示錄
    正文 我和宋清朗相戀三年，在試婚紗的時(shí)候發(fā)現(xiàn)自己被綠了活喊。 大學(xué)時(shí)的朋友給我發(fā)了我未婚夫和他白月光在一起吃飯的照片丐膝。...
    茶點(diǎn)故事閱讀 40,865評論 1贊 353
  • 活死人
    序言：一個(gè)原本活蹦亂跳的男人離奇死亡，死狀恐怖钾菊，靈堂內(nèi)的尸體忽然破棺而出尤误，到底是詐尸還是另有隱情，我是刑警寧澤结缚，帶...
    沈念sama閱讀 36,527評論 5贊 351
  • ?日本核電站爆炸內(nèi)幕
    正文 年R本政府宣布损晤，位于F島的核電站，受9級特大地震影響红竭，放射性物質(zhì)發(fā)生泄漏尤勋。R本人自食惡果不足惜，卻給世界環(huán)境...
    茶點(diǎn)故事閱讀 42,211評論 3贊 336
  • 男人毒藥：我在死后第九天來索命
    文/蒙蒙 一茵宪、第九天 我趴在偏房一處隱蔽的房頂上張望最冰。 院中可真熱鬧，春花似錦稀火、人聲如沸暖哨。這莊子的主人今日做“春日...
    開封第一講書人閱讀 32,699評論 0贊 25
  • 一樁弒父案凰狞，背后竟有這般陰謀
    文/蒼蘭香墨 我抬頭看了看天上的太陽篇裁。三九已至，卻和暖如春赡若，著一層夾襖步出監(jiān)牢的瞬間达布，已是汗流浹背。 一陣腳步聲響...
    開封第一講書人閱讀 33,814評論 1贊 274
  • 情欲美人皮
    我被黑心中介騙來泰國打工逾冬， 沒想到剛下飛機(jī)就差點(diǎn)兒被人妖公主榨干…… 1. 我叫王不留黍聂，地道東北人躺苦。 一個(gè)月前我還...
    沈念sama閱讀 49,299評論 3贊 379
  • 代替公主和親
    正文 我出身青樓，卻偏偏與公主長得像产还，于是被迫代替她去往敵國和親匹厘。 傳聞我的和親對象是個(gè)殘疾皇子，可洞房花燭夜當(dāng)晚...
    茶點(diǎn)故事閱讀 45,870評論 2贊 361

推薦閱讀更多精彩內(nèi)容