Databases
StackOverflow2013
Postsdbo
POSending message from service to UI-Thread - Messages delayed in service's handler
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSending message from service to UI-Thread - Messages delayed in service's handler
    primarykey
    data
    text
    <p>I have a service which is pulling data from the server. And I have activity as gui which needs to get updated.</p> <p>So on different occassions, e.g. the information was pulled from the server successfully, the server must signal the activity that there is new information.</p> <p>For this I implemented this function:</p> <pre><code> /** * ServerService.class * * Sends a message to the observer that there is a new status message to be * pulled from the service# * * @param pMessage * the message to be set to the public status */ private void signalNewStatus(String pMessage) { //check if there is a message at all to be signaled as new if (pMessage != null) { Log.v(tag, "signalNewStatus:" + pMessage); // set the message vStatus = pMessage; // start the new callback via the handler myMessageHandler.sendEmptyMessage(I_STATUS_UPDATE_SIGNAL); } } </code></pre> <p>To handle the messages, I have the message handler:</p> <pre><code> private final Handler myMessageHandler = new Handler() { @Override public void handleMessage(Message msg) { Log.i(tag, "handleMessage: "+msg.what); switch (msg.what) { case I_STATUS_UPDATE_SIGNAL: { // Broadcast to all clients the new value. final int N = myCallbackList.beginBroadcast(); for (int i = 0; i &lt; N; i++) { try { myCallbackList.getBroadcastItem(i).sendUpdateStatusSignal(true); } catch (RemoteException e) { } } myCallbackList.finishBroadcast(); } break; </code></pre> <p>The first function is called quite often, and I can see in the logging that this works right on time. </p> <p>But the logging for the message handling does not get called right away. It is delayed and gets called most often at the end. Somehow as bulk.</p> <p>I cannot figure out why this is the case. The rest works well, the message gets to the UI thread without a problem once the message was handled. </p> <p>Any suggestions?</p> <p>Thanks a lot!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USuser929995
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSending message from service to UI-Thread - Messages delayed in service's handler
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSending message from service to UI-Thread - Messages delayed in service's handler
      1. This table or related slice is empty.
      1. VTUpMod
    1. COJust thought about messages collision. May be some others sends messages a lot and blocking/creating delay on this message.
      singulars
      1. POSending message from service to UI-Thread - Messages delayed in service's handler
      1. USVolodymyr Lykhonis
    2. CONo, it is not the problem with the receiver of the message (UI Thread), the problem occurs on the service side. And only the service can send a message from within itself.
      singulars
      1. POSending message from service to UI-Thread - Messages delayed in service's handler
      1. USuser929995
 

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