7 messages in com.googlegroups.google-gears[gears-users] Re: Application Deploym...| From | Sent On | Attachments |
|---|---|---|
| genericallyloud | 28 Jul 2008 06:02 | |
| Chris Prince | 28 Jul 2008 14:03 | |
| Brad Neuberg | 28 Jul 2008 16:42 | |
| Brad Neuberg | 28 Jul 2008 16:47 | |
| genericallyloud | 29 Jul 2008 17:17 | |
| Michael Nordman | 29 Jul 2008 17:27 | |
| Scott Hess | 29 Jul 2008 17:37 |
| Subject: | [gears-users] Re: Application Deployment - HTML5 |
|---|---|
| From: | Michael Nordman (mich...@google.com) |
| Date: | 07/29/2008 05:27:43 PM |
| List: | com.googlegroups.google-gears |
Definitely worth some thought. Getting a coherent set of resources that comprise the 'application' has been a pain point.
A related idea is to download a fully formed 'database' file which can them be accessed via scriptable database api's. This could reduce the number of distinct requests to retrieve the relevant data and remove altogether local SQL inserts and updates to build up the local database file.
On Mon, Jul 28, 2008 at 6:03 AM, genericallyloud <Russ...@gmail.com>wrote:
I just sent this feature request to the whatwg mailing list, and I thought I would toss it this way as well. Basically, the pain point is that extra http requests are a real performance hit and large web apps tend to have to do a lot of work to get down to the fewest requests as possible. The suggestion is that there be a way to load a zip or tar file that can be used as way of priming the cache (or other storage mechanism) so that other resource requests do not require a trip to the server. For example, instead of creating css sprites, all images could go into the zip file, and still be loaded in one trip, then when the css required it, it would be pulled from the cache instead of requiring the trip to the server.
This seemed like something that could also tie in nicely to the local server mechanism.
Here's a link to the whatwg mailing list post: http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2008-July/015411.html.