-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Of interest.
- -------- Original Message -------- Subject: 2.0 and Radio Impacts/battery efficiency Resent-Date: Thu, 12 Apr 2012 08:53:01 +0000 Resent-From: [email protected] Date: Thu, 12 Apr 2012 10:52:18 +0200 From: Salvatore Loreto <[email protected]> To: HTTP Working Group <[email protected]> Hi there, here a good read about "Optimizing Downloads for Efficient Network Access" http://developer.android.com/training/efficient-downloads/efficient-network-access.html the major points are 1) reducing the number of connections is a MUST as each new network connection is extremely expensive from a Radio/Battery prospective It is also worth to add that the server-initiated closing of idle connection is also something to avoid. So if the client keeps the connection open longer, then the specification has to mandate servers to keep the connection open for very long. 2) the ping frequency is also very important: /"An app that pings the server every 20 seconds, just to acknowledge that the app is running and visible to the user, will keep the radio powered on indefinitely" / 3) also Prefetching data need some consideration from the radio prospective as Prefetching data (on a wireless connection) may cost money but for sure has a cost from a battery prospective cheers Sal - -- Salvatore Loreto, PhD www.sloreto.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+Gz8wACgkQNL8k5A2w/vxStwCeNKkyq5onTQ6JCrJ7vDeYGWcN U9IAn2NAda3BPW7yXyoyztAgy5QxrNnJ =T2Dv -----END PGP SIGNATURE-----
