StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20860706
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
5
CommunityOwnedDate
CreationDate
2013-12-31T16:59:27.310
FavoriteCount
0
LastActivityDate
2013-12-31T18:27:14.220
LastEditDate
2013-12-31T18:27:14.220
LastEditorUserId
357055
OwnerUserId
357055
ParentId
20857101
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
From the <a href="http://developer.android.com/guide/components/aidl.html" rel="nofollow">AIDL docs</a>: <blockquote> By default, RPC calls are synchronous. If you know that the service takes more than a few milliseconds to complete a request, you should not call it from the activity's main thread, because it might hang the application (Android might display an "Application is Not Responding" dialog)—you should usually call them from a separate thread in the client. </blockquote> When you call a method on your <code>IBinder</code> instance to do the HTTP request, the calling thread (in this case, probably the UI thread) is blocking and triggering the exception. To take advantage of the service's background thread, you should send work to it through an <code>Intent</code>. Depending on your requirements, an <code>IntentService</code> or an <code>AsyncTask</code> may be a better approach. If you use an <code>IntentService</code> (even in the same app process), the <code>Intent</code> will be handled on a background thread. You will need a mechanism for sending results back to the client (your <code>Activity</code> in this case); I've used a <code>BroadcastReceiver</code> for this purpose. If your service only makes short HTTP requests and returns the results to an <code>Activity</code>, then an <code>AsyncTask</code> will be much simpler to implement. EDIT: I think there is some confusion about how Android handles threads. The problem with your architecture is that you're calling a long-running method on an <code>IBinder</code> object, and you're calling it from the UI thread of your app. This type of RPC call will block while the method runs and will cause the exception that you're describing. The recommended way to send long-running work to a service is through an <code>Intent</code>. As I said earlier, an <a href="http://developer.android.com/reference/android/app/IntentService.html" rel="nofollow"><code>IntentService</code></a> will handle its intents in a background thread automatically and doesn't need a separate process. (A separate process is generally needed only if the service is likely to crash and you don't want it to bring down the app.)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POBinder Service as a Separate Thread
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USacj
UserOwnerUserId
1. USacj
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

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.