StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16428024
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-05-07T20:30:37.127
FavoriteCount
0
LastActivityDate
2013-05-29T17:16:15.317
LastEditDate
2013-05-29T17:16:15.317
LastEditorUserId
111307
OwnerUserId
111307
ParentId
1728631
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
NSURLRequests are completely asynchronous anyway. If you need to make an NSURLRequest from a thread other than the main thread, I think the best way to do this is just make the <code>NSURLRequest</code> from the main thread. <pre><code>// Code running on _not the main thread_: [self performSelectorOnMainThread:@selector( SomeSelectorThatMakesNSURLRequest ) withObject:nil waitUntilDone:FALSE] ; // DON'T block this thread until the selector completes. </code></pre> All this does is shoot off the HTTP request from the main thread (so that it actually works and doesn't mysteriously disappear). The HTTP response will come back into the callbacks as usual. If you want to do this with GCD, you can just go <pre><code>// From NOT the main thread: dispatch_async( dispatch_get_main_queue(), ^{ // // Perform your HTTP request (this runs on the main thread) } ) ; </code></pre> The <code>MAIN_QUEUE</code> runs on the main thread. So the first line of my HTTP get function looks like: <pre><code>void Server::get( string queryString, function<void (char*resp, int len) > onSuccess, function<void (char*resp, int len) > onFail ) { if( ![NSThread isMainThread] ) { warning( "You are issuing an HTTP request on NOT the main thread. " "This is a problem because if your thread exits too early, " "I will be terminated and my delegates won't run" ) ; // From NOT the main thread: dispatch_async( dispatch_get_main_queue(), ^{ // Perform your HTTP request (this runs on the main thread) get( queryString, onSuccess, onFail ) ; // re-issue the same HTTP request, // but on the main thread. } ) ; return ; } // proceed with HTTP request normally } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAsynchronous request to the server from background thread
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USbobobobo
UserOwnerUserId
1. USbobobobo
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
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.