3 ms·

Apple really needs to allow applications access to a modified launchd -- instead of running in the background, allow apps to register programs to execute on eve

by blasdel 17y ago

Apple really needs to allow applications access to a modified launchd -- instead of running in the background, allow apps to register programs to execute on events like "every half hour" or "when my location changes by 200m", with the events unified into batches. The only remaining reason to run in the background would be for playing audio.

nudded 17y ago
this has been said over and over again. The main problem with this is that: 1) the battery would not last as long as Apple wants it to 2) what if 2 applications receive a notification at the same time? how can this be handled (what if 7 apps at the same time?) 3) there is not enough ram available for apps to stay in memory, and when an app receives a notification it should than be started with this notification.
- jrockway 17y ago
  the battery would not last as long as Apple wants it to The battery lasts even longer if you turn your phone off. Of course, you have no functionality, but who cares... great battery life! what if 2 applications receive a notification at the same time? how can this be handled (what if 7 apps at the same time?) Say hello to my little friend "loop". there is not enough ram available for apps to stay in memory, and when an app receives a notification it should than be started with this notification If the app can't handle the notification quickly, then it can be dropped on the floor. This is Google Latitude, not a controller telling your heart when to beat. Also, handling notifications doesn't require the entire app to be available. When I process emails, the only thing that actually runs is a tiny script to insert a record into the database. The intense processing can happen latter. In the case of Google Maps, the GPS location is passed in as an argument to a tiny script, which makes one HTTP POST request. If that takes too much memory, then the iPhone really, really sucks.

by blasdel 17y ago

nudded 17y ago

this has been said over and over again. The main problem with this is that: 1) the battery would not last as long as Apple wants it to 2) what if 2 applications receive a notification at the same time? how can this be handled (what if 7 apps at the same time?) 3) there is not enough ram available for apps to stay in memory, and when an app receives a notification it should than be started with this notification.

jrockway 17y ago
the battery would not last as long as Apple wants it to The battery lasts even longer if you turn your phone off. Of course, you have no functionality, but who cares... great battery life! what if 2 applications receive a notification at the same time? how can this be handled (what if 7 apps at the same time?) Say hello to my little friend "loop". there is not enough ram available for apps to stay in memory, and when an app receives a notification it should than be started with this notification If the app can't handle the notification quickly, then it can be dropped on the floor. This is Google Latitude, not a controller telling your heart when to beat. Also, handling notifications doesn't require the entire app to be available. When I process emails, the only thing that actually runs is a tiny script to insert a record into the database. The intense processing can happen latter. In the case of Google Maps, the GPS location is passed in as an argument to a tiny script, which makes one HTTP POST request. If that takes too much memory, then the iPhone really, really sucks.