Strict Standards: Non-static method utf_normalizer::nfc() should not be called statically in /www/htdocs/w006661d/anddev/includes/utf/utf_tools.php on line 1781
[phpBB Debug] PHP Notice: in file /includes/session.php on line 1007: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)
[phpBB Debug] PHP Notice: in file /includes/session.php on line 1007: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)
[phpBB Debug] PHP Notice: in file /includes/session.php on line 1007: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)

Strict Standards: Non-static method utf_normalizer::nfc() should not be called statically in /www/htdocs/w006661d/anddev/includes/utf/utf_tools.php on line 1781
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4362: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4364: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4365: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4366: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)
anddev.org • View topic - Download content in background

Download content in background

Your ideas for any killerapplication that comes to your mind ;)

Download content in background

Postby billhamlin » Sat Nov 14, 2009 12:44 am

I've been thinking of an application that addresses the problem of slow internet speeds. Essentially, the application would remember URLs to fetch, and would do so during the day -- or on some configured interval. This content would be available when the user wants to see it.

The background request would indicate in an HTTP header that the response can be "when available" (we can get into details of how that would be done). So the network leaks out the response when bandwidth is available.

I suppose there is a major problem in that the phone is typically "off" and so is not ready to receive this data. (Or is it? Sometimes I'll ask for a webpage and get bored waiting for the response and hit the red button, only to find that the page is there when I look a few minutes later.)

I'd be interested in any comments about this idea that anyone may have.

Thanks,
Bill
billhamlin
Once Poster
Once Poster
 
Posts: 1
Joined: Sat Nov 14, 2009 12:37 am

Top

Return to Creative Corner

Who is online

Users browsing this forum: No registered users and 1 guest