Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>A callback method/listener is the right thing to do. (As CommonsWare says, it's pretty much the same thing). I would say it's much simpler than fiddling around with BroadcastReceivers, since you're already using aidl.</p> <p>Something like this:</p> <p><strong>IAsyncThing.aidl:</strong></p> <pre><code>package com.my.thingy; import com.my.thingy.IAsyncThingListener; interface IAsyncThing { void doSomething(IAsyncThingListener listener); } </code></pre> <p><strong>IAsyncThingListener.aidl:</strong></p> <pre><code>package com.my.thingy; import com.my.thingy.IAsyncThingListener; interface IAsyncThingListener { void onAsyncThingDone(int resultCodeIfYouLike); } </code></pre> <p>You can enforce that only your apps can bind to the service by using a signature-level permission on your service (see the note on 'service permissions' here: <a href="http://developer.android.com/guide/topics/security/permissions.html">http://developer.android.com/guide/topics/security/permissions.html</a>). Specifically:</p> <ul> <li>Declare a permission in your service's <code>AndroidManifest.xml</code>. Ensure it is <code>signature</code> level.</li> <li>Add that permission in your <code>service</code> tag</li> <li>In all the other apps, use <code>uses-permission</code> to use it.</li> </ul> <p>A couple of other things to bear in mind:</p> <ul> <li>In the caller, you'll need to subclass <code>IAsyncThingListener.Stub</code>. Your calling application code may already be subclassing something else, so that means you'd have to use an extra (probably inner) class to receive the completion notification. I mention this only because this might be the answer to question #2 - which I don't fully understand.</li> <li>If the service is potentially in different processes from the caller, each should register for death notification of the other using <code>IBinder.linkToDeath</code>.</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POAndroid remote service callbacks
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USAdrian Taylor
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POAndroid remote service callbacks
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhat happens if my service calls the callback and the bound application is no longer active / was moved to the background, or was killed by the system?
      singulars
      1. PO
      1. USAndroid QS
    2. COThat's what the `IBinder.linkToDeath` bit is for. You'll get told if the application is killed. In all other circumstances (e.g. it's in the background) all the IPC communication should still work fine.
      singulars
      1. PO
      1. USAdrian Taylor
    3. COIf the app's activity binds to my service and makes an async request, but is no longer active (not on-screen) when the callback is called, the callback function is still received? Wouldn't the private callback stub object be destroyed when the activity is destroyed?
      singulars
      1. PO
      1. USAndroid QS
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload