- Joined
- Jul 24, 2008
- Messages
- 1
- Reaction score
- 0
- Points
- 1
Thinking about this a little more... "Push" is supposed to mean that the server contacts the client when it needs to update some data. What is confusing us here is that the definition of push over HTTP is not strictly correct. HTTP is a 'stateless protocol'. The server cannot contact the client when it needs to send an update. The server can only respond to a request from the client on a one-time basis. To work around this limitation, the browser needs to constantly poll the server in order to get the updates.
However, this isn't a browser, it's a phone, which is a two-way communication device. It *IS* possible to receive incoming messages with a phone. How else would people be able call you?! I'm not sure if the push implementation on the iPhone is using this feature of the phone but it *is* possible to have real push technology on a device such as a phone.
Therefore, it may be that push could save battery life. However, I've tried all of the options and it does not appear to be the culprit causing poor battery life. I suspect it's related to having used an application that continues to run in the background. Even if the phone is no longer in use, the battery is drained within a few hours.
However, this isn't a browser, it's a phone, which is a two-way communication device. It *IS* possible to receive incoming messages with a phone. How else would people be able call you?! I'm not sure if the push implementation on the iPhone is using this feature of the phone but it *is* possible to have real push technology on a device such as a phone.
Therefore, it may be that push could save battery life. However, I've tried all of the options and it does not appear to be the culprit causing poor battery life. I suspect it's related to having used an application that continues to run in the background. Even if the phone is no longer in use, the battery is drained within a few hours.
