Main question: Is there a special reason why ServiceStartArguments uses a PendingIntent based on AlarmService.class instead of ServiceStartArgumentsController?
For my own education: I'm trying to decide which example of the services I should be modeling my networking code after in order to get the desired functionality. Basically, my app is storing data that will be uploaded when 1) the user hits a button or 2) on startup if not all the data has been uploaded yet. The uploading is naturally taking place in the background while the app runs. I'm planning on running it in the same process, as I don't seem to have a burning need to do otherwise, so I'm assuming I don't need IPC for it. I'm also assuming that, because the other services never die upon backing out of the app, that if the user backs out of my app the uploading will not be interrupted. I'm not way off base here, am I? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
