Activity, Service & Code sit in a bar...
No, not a beginning of a joke, and not in a bar but in memory.
Here's the situation:
Activity A starts service S. There's also a code module C (C's subs are used by both A and S)
Activity A can be closed (by user) and the service S will still be running. If the service issues a notification then A can be brought up again by clicking the notification.
questions:
1) If A is "kicked out" of memory because memory management requires so, what happens to C?
2) Can C be "kicked out" as well if memory management decides to do that?
3) when A is "out of memory" (and C is too) , Can S still call subs within C?
No, not a beginning of a joke, and not in a bar but in memory.
Here's the situation:
Activity A starts service S. There's also a code module C (C's subs are used by both A and S)
Activity A can be closed (by user) and the service S will still be running. If the service issues a notification then A can be brought up again by clicking the notification.
questions:
1) If A is "kicked out" of memory because memory management requires so, what happens to C?
2) Can C be "kicked out" as well if memory management decides to do that?
3) when A is "out of memory" (and C is too) , Can S still call subs within C?
