Yes. But you're going to have a unique TCP connection per host, at minimum.
Unless I'm misunderstanding the problem you're raising, it seems like a non-issue for the majority of people with multiple accounts (a work email, a Gmail, a hotmail; for instance).
A unique connection per host isn't too bad. But I have 12 connections for each of my desktops and laptops and phones and tablets...
As you say the problem is somewhat caused by Apple ~~and Google~~ forcing apps to use their proprietary notification systems so that e.g., mail can be checked while a phone is idling. But the end user does not care about the market abusing power of the monopolies--they wants instant notifications when they receive mail...
Google is _not_ forcing, only Apple is. This cannot be emphasized enough.
You can still perfectly have dozens of background TCP connections idling on Android with no issue. The only caution you need to take is to synchronize the keepalives (otherwise the radio may take stay on for too long, hitting your battery life), but this was solved back when Android was still Danger.
As evidenced by the power analysis of IM apps that was here on HN a couple weeks ago, there is no discernible advantage to using Google notifications versus just keeping your multiple TCP connections idling in the background: Conversations is a Jabber client which does the second and was practically the most power-friendly client of the entire Android ecosystem.
> A unique connection per host isn't too bad. But I have 12 connections for each of my desktops and laptops and phones and tablets...
It's host<->host unique. So, assuming your email server allows enough keepalives, you're fine with multiple devices.
Where you might have an issue is if you have multiple accounts on the same server (not even the same service, necessarily; Gmail, hotmail, etc have a plethora of servers) and connect to them via the same device.
Yes. But you're going to have a unique TCP connection per host, at minimum.
Unless I'm misunderstanding the problem you're raising, it seems like a non-issue for the majority of people with multiple accounts (a work email, a Gmail, a hotmail; for instance).
A unique connection per host isn't too bad. But I have 12 connections for each of my desktops and laptops and phones and tablets...
As you say the problem is somewhat caused by Apple ~~and Google~~ forcing apps to use their proprietary notification systems so that e.g., mail can be checked while a phone is idling. But the end user does not care about the market abusing power of the monopolies--they wants instant notifications when they receive mail...
Google is _not_ forcing, only Apple is. This cannot be emphasized enough.
You can still perfectly have dozens of background TCP connections idling on Android with no issue. The only caution you need to take is to synchronize the keepalives (otherwise the radio may take stay on for too long, hitting your battery life), but this was solved back when Android was still Danger.
As evidenced by the power analysis of IM apps that was here on HN a couple weeks ago, there is no discernible advantage to using Google notifications versus just keeping your multiple TCP connections idling in the background: Conversations is a Jabber client which does the second and was practically the most power-friendly client of the entire Android ecosystem.
1 reply →
> A unique connection per host isn't too bad. But I have 12 connections for each of my desktops and laptops and phones and tablets...
It's host<->host unique. So, assuming your email server allows enough keepalives, you're fine with multiple devices.
Where you might have an issue is if you have multiple accounts on the same server (not even the same service, necessarily; Gmail, hotmail, etc have a plethora of servers) and connect to them via the same device.