Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>Which one is best for continuous/time-wise server updates?</p> </blockquote> <p>depends if your app suppose to run in background / foreground at that time:</p> <p>let's say you are scheduling <code>Runnable</code> via handler to 15 minutes from now.<br> if the user will "close" all running activities, the system will probably kill your process if it not running any foreground services/activities after a while to reclaim memory. in that case - your <code>Runnable</code> will never be executed.<br> if you want to continuously poll for server updates even when the user navigates away from your app - this option is obviously not good for you. if you choose to update server like that - at least do it from a started <code>Service</code> context- that way your Handler reference will stay allocated even when user navigates from one screen to another...</p> <p>on the other hand - providing pending intent to <code>AlarmManager</code> insures that no mater if your process is alive or not - the intent provided to the <code>AlarmManager</code> will wake up your app (and the Service / Activity / broadcast) you provided with the pending intent.</p> <p>about your question - I think that <strong>none of the two</strong> are good solution to get server updates: </p> <p>the user probably have 10-20 applications (such Facebook/Twitter/Whattsap/Viber/Google+...) installed on his device which getting updates from server. imagine that each one of them wake up in some different time interval, opens internet connections, consuming lot's of precious battery life and band-width. <strong>that's crazy!</strong> your device will never "sleep", all process will be opened all the time, internet cellular radio transmission also. the battery will rich to 0% very fast! </p> <p>the right think to do is to use the GCM API. it requires also server side implementation, but the general idea is that the responsibility to wake up your application when there is a new data passes to the server's side, and by that -the android application don't need to poll for updates. it just get notified (and wake up if the process not alive) when the server notified you. in case you'll wonder - this is how it works - <a href="https://stackoverflow.com/questions/11508613/how-does-push-notification-technology-work-on-android/11508811#11508811">How does push notification technology work on Android?</a></p> <p>I advice you to read about it - <a href="http://developer.android.com/google/gcm/index.html" rel="nofollow noreferrer">http://developer.android.com/google/gcm/index.html</a></p>
    singulars
    1. This table or related slice is empty.
    1. POAndroid: Looper vs AlarmManager
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USTal Kanel
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POAndroid: Looper vs AlarmManager
      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. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. CO+1 for a good advice. Nice explanation and also very useful for me and many developers. But can you help me to understand why you always prefer GCM( Google Cloud Messaging) . And how this is helpful for time-wise sending/receiving data to server (for ex: gps tracking apps always have to do such kind of things). Is this the perfect decision to use a tough and new thing for this work . Or we will continue with the previous ones(AlalamManager/Looper).
      singulars
      1. PO
      1. USRanjit
    2. COOk ..Its good when we require the updated server data. i.e when server will found some new data it will immediately push it to the client. Fine. but what about the client(vice versa) ? how it will send continuous updated datas (ex: latitude, longitude) to the server..
      singulars
      1. PO
      1. USRanjit
    3. COI explained you exactly why it's much better. you did not mentioned in your question anything about the opposite direction (sending to the server your current location). anyway - if you want to send the server information when location changed - you have to do it carefully because the reasons I already mentioned. and your question "using Handlers vs AlarmManager" is not relevant - because if you are using google best practices - you have to set explicitly location listener callback or provide pending intent. there's nothing to do here with handler
      singulars
      1. PO
      1. USTal Kanel
 

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