Core Data淺談係列之八 : 關於並發
有時候,我們需要有個worker thread來做一些密集型或者長耗時的任務,以避免阻塞住UI,給用戶不好的體驗。比如從網絡上獲取一批數據,然後解析它們,並將其輸出到存儲文件中。這時候,由於數據層發生了變動,我們希望通知到主線程更新UI —— 這就涉及到Core Data的多線程特性。比如我們一直以來使用的Demo中,添加球員信息的AddPlayerViewController和顯示球員列表的PlayerListViewController在進行CURD操作時都是在主ViewController的context中完成的,這通過維持一個屬性cdViewController指向主ViewController來實現:
#pragma mark -
#pragma mark - UITableView Delegate
- (void)tableView:(UITableView *)tableView didSelectRowAtIndexPath:(NSIndexPath *)indexPath
{
[tableView deselectRowAtIndexPath:indexPath animated:YES];
Team *teamObject = [self.teamArray objectAtIndex:indexPath.row];
PlayerListViewController *playerListVC = [[[PlayerListViewController alloc] init] autorelease];
playerListVC.team = teamObject;
playerListVC.cdViewController = self;
[self.navigationController pushViewController:playerListVC animated:YES];
}
以及:#pragma mark -
#pragma mark - Player CURD
- (void)addPlayer:(id)sender
{
AddPlayerViewController *addPlayerVC = [[[AddPlayerViewController alloc] init] autorelease];
addPlayerVC.cdViewController = self.cdViewController;
addPlayerVC.team = self.team;
[self presentModalViewController:addPlayerVC animated:YES];
}
對於比較小的Demo,這麼寫代碼是可以接受的,雖然也會覺得傳遞得有點長。
當程序的代碼規模比較大,或者說處理的數據比較多時,我們可以通過引入並發特性來做一點優化。
通過創建臨時的context來添加球員信息:
- (IBAction)addBtnDidClick:(id)sender
{
dispatch_async(dispatch_get_global_queue(DISPATCH_QUEUE_PRIORITY_DEFAULT, 0), ^{
NSManagedObjectContext *tmpContext = [[NSManagedObjectContext alloc] init];
[tmpContext setPersistentStoreCoordinator:sharedPersistentStoreCoordinator];
// We don't check the user input.
Player *playerObject = [NSEntityDescription insertNewObjectForEntityForName:@"Player" inManagedObjectContext:tmpContext];
playerObject.name = self.nameTextField.text;
playerObject.age = [NSNumber numberWithInteger:[self.ageTextField.text integerValue]];
playerObject.team = self.team;
NSError *error = NULL;
if (tmpContext && [tmpContext hasChanges] && ![tmpContext save:&error]) {
NSLog(@"Error %@, %@", error, [error localizedDescription]);
abort();
}
dispatch_async(dispatch_get_main_queue(), ^{
[self dismissModalViewControllerAnimated:YES];
});
});
}
為了響應其它線程的變化,參考此文檔,我們可以先監聽消息,然後合並發生了的變化:[[NSNotificationCenter defaultCenter] addObserver:self selector:@selector(mocDidSaveNotification:) name:NSManagedObjectContextDidSaveNotification object:nil];
- (void)mocDidSaveNotification:(NSNotification *)notification
{
NSManagedObjectContext *savedContext = [notification object];
if (savedContext == self.managedObjectContext) {
return ;
}
if (savedContext.persistentStoreCoordinator != self.persistentStoreCoordinator) {
return ;
}
dispatch_async(dispatch_get_main_queue(), ^{
NSLog(@"Merge changes from other context.\n");
[self.managedObjectContext mergeChangesFromContextDidSaveNotification:notification];
});
}
這麼做了之後,我們嚐試添加一名球員,會得到如下錯誤信息:
2013-01-21 09:56:08.300 cdNBA[573:617] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'Illegal attempt to establish a relationship 'team' between objects in different contexts這是由於我們把主線程context中的team對象傳遞到臨時創建的context中進行操作了。在Core Data的多線程環境中,我們隻能傳遞objectID或者重新fetch:
addPlayerVC.teamID = [self.team objectID]; // ... playerObject.team = (Team *)[tmpContext objectWithID:self.teamID];這樣可以執行過去,控製台輸出:
2013-01-21 10:11:12.834 cdNBA[687:1b03] void _WebThreadLockFromAnyThread(bool), 0x83a91c0: Obtaining the web lock from a thread other than the main thread or the web thread. UIKit should not be called from a secondary thread. 2013-01-21 10:11:12.932 cdNBA[687:c07] Merge changes from other context.
第二行日誌說明合並變化了,不過第一行告訴我們在非主線程裏麵訪問了一些UI方麵的東西。這是由於上麵在global_queue裏麵訪問了UITextField,把訪問UI的代碼提到外麵即可。
BTW,在iOS 5以後,蘋果提供了更為便捷有效的parent-child context機製,可以參見這裏。
Brief Talk About Core Data Series, Part 8 : About Concurrency
Jason Lee @ Hangzhou
Weibo : https://weibo.com/jasonmblog
最後更新:2017-04-04 07:03:40