3 ms·
No, I don't think you understand my argument. >This or that supplied function covers your need, you can pass it. Sorry, you can't make yours, what would you po
by loewenskind 16y ago
No, I don't think you understand my argument.
>This or that supplied function covers your need, you can pass it. Sorry, you can't make yours, what would you possibly want?
We've had concurrency and services for decades, we already know every general action you can possibly do with a service. No one is going to come up with some totally new novel use for a background service anymore than anyone will come up with a new general action to apply to lists. Everything you would ever want to do with a background service can be divided into about 5 kinds of tasks and those are covered. Full stop.
If you disagree then please describe some act with a service and I'll explain to you how that already fits in one of the 4 or 5 kinds of things people do with services. Proposing that some day, some where someone may come up with something that doesn't fit this mold is just hand waving.
- orangecat 16y agoEverything you would ever want to do with a background service can be divided into about 5 kinds of tasks and those are covered. AFAIK it's not possible to simply keep an SSH or IM connection open when you switch to another app.
- loewenskind 16y agoYou can have your app continue to run for up to 10 minutes after it's been closed, so it should be possible to use that time to keep your connection open. If no one has contacted you in 10 minutes then chances are they wont in the next 10 either so it would be better to switch to push notification and let the phone manage notifications. Keeping SSH or IM connections open is an action of a well known use for servers; listening for updates. And that's covered in the API.