W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2012

2.0 and Radio Impacts/battery efficiency

From: Salvatore Loreto <salvatore.loreto@ericsson.com>
Date: Thu, 12 Apr 2012 10:52:18 +0200
Message-ID: <4F8697C2.5000702@ericsson.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
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
Received on Thursday, 12 April 2012 08:52:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:52:00 GMT