StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9662732
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-03-12T06:41:38.037
FavoriteCount
0
LastActivityDate
2012-03-12T06:41:38.037
LastEditDate
LastEditorUserId
0
OwnerUserId
381870
ParentId
9659410
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
As you said, you need to balance <code>beginBackgroundTaskWithExpirationHandler</code> call with an <code>endBackgroundTask</code> call. One solution I have in mind looks like this: Create a new instance variable <pre><code>UIBackgroundTaskIdentifier backgroundTaskID; </code></pre> You are counting the requests anyway so you could also decrement getRequest in connectionDidFinishLoading: <pre><code>- (void)connectionDidFinishLoading:(NSURLConnection *)connection { // process data from server getRequest--; if (getRequest == 0 && backgroundTaskID != UIBackgroundTaskInvalid) { [[UIApplication sharedApplication] endBackgroundTask:backgroundTaskID]; backgroundTaskID = UIBackgroundTaskInvalid; } } </code></pre> Now the background task gets ended after the last request has been completed. To start only one background task you start it in a method that gets called when the app goes to the background. You need to listen for the <code>UIApplicationDidEnterBackgroundNotification</code> <pre><code>[[NSNotificationCenter defaultCenter] addObserver:self selector:@selector(applicationDidEnterBackground) name:UIApplicationDidEnterBackgroundNotification object:nil]; </code></pre> and implement the method <pre><code>- (void)applicationDidEnterBackground:(NSNotification *)notification { if (getRequest > 0) { backgroundTaskID = [[UIApplication sharedApplication] beginBackgroundTaskWithExpirationHandler:^{ [[UIApplication sharedApplication] endBackgroundTask:backgroundTaskID]; backgroundTaskID = UIBackgroundTaskInvalid; }]; } } </code></pre> Now you only have one running background task that starts automatically when your app goes to the background and you have running requests that gets ended when all your requests are done. Another improvement would be to add your network requests to an NSOperationQueue to avoid the manual counting and limit the number of concurrent requests.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUsing multiple beginBackgroundTaskWithExpirationHandler calls
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. UStim
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POUsing multiple beginBackgroundTaskWithExpirationHandler calls
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.