Re: [whatwg] Google Gears and HTML5

On Wed, 30 May 2007, Maciej Stachowiak wrote: > > One thing I'd like to see is some reconciliation between the SQL API and > the Storage interface. These are two completely separate storage > mechanisms with different security policies, different access APIs (SQL > queries vs. simple key/value p

Re: [whatwg] Google Gears and HTML5

On Tue, 9 Oct 2007, Dave Camp wrote: > On 10/9/07, Ian Hickson <[EMAIL PROTECTED]> wrote: > > I've now added an offline Web applications system to HTML5. Comments > > welcome. > > One small nit, swapCache() should probably set the state back to IDLE. Actually, the "update ready" state was an erro

Re: [whatwg] Google Gears and HTML5

On Tue, 9 Oct 2007, Chris Prince wrote: > > > > So how does a page, once cached, stop being cached? There doesn't seem > > to be a way to end the caching. In HTML5's model, you have to leave a > > blank manifest file forever (or until all your users have been weened > > off the old cache manifes

Re: [whatwg] Google Gears and HTML5

On 10/9/07, Ian Hickson <[EMAIL PROTECTED]> wrote: > I've now added an offline Web applications system to HTML5. Comments > welcome. One small nit, swapCache() should probably set the state back to IDLE. -dave

Re: [whatwg] Google Gears and HTML5

On 10/9/07, Ian Hickson <[EMAIL PROTECTED]> wrote: > On Fri, 1 Jun 2007, Chris Prince wrote: > > That is correct. Gears starts serving a manifest's resources only when > > everything has been successfully downloaded. If it gets a 404 it will > > try again later. > > So how does a page, once cache

Re: [whatwg] Google Gears and HTML5

(This thread covered several topics. I'm focussing on the offline web apps aspects only at the moment. I shall return to this thread in the future for the other aspects.) On Wed, 30 May 2007, Maciej Stachowiak wrote: > > Now that Google Gears has been announced, I'd

Re: [whatwg] Google Gears and HTML5

On 6/12/07, Aaron Boodman (Google) <[EMAIL PROTECTED]> wrote: On 6/11/07, Robert O'Callahan <[EMAIL PROTECTED]> wrote: > Chris Prince wrote: > How do you do that when an ambiguity is discovered during a manifest update? That's a good point, i think all we could do there is throw into the enviro

Re: [whatwg] Google Gears and HTML5

On 6/12/07, Chris Prince <[EMAIL PROTECTED]> wrote: > what's the use case for "remove" Without it, once you put a given URL in the ResourceStore, it would be served from there forever. Also, remember that the ResourceStore doesn't auto-update URL contents like the ManagedResourceStore does. >

Re: [whatwg] Google Gears and HTML5

> Gears returns an error when you first try to setup an ambiguous > capture. How do you do that when an ambiguity is discovered during a manifest update? We hadn't thought about the case where the ambiguity is caused by a manifest's new contents. Thanks for pointing that out. what's the use

[whatwg] Google Gears and HTML5

Chris Prince wrote: Gears returns an error when you first try to setup an ambiguous capture. How do you do that when an ambiguity is discovered during a manifest update? Since you're here, I'm curious about the motivation for a few of the Gears features. In particular, what's the use case for

Re: [whatwg] Google Gears and HTML5

> It's not clear what the Gears ManagedStore does > if it gets a 404 or some other error during an update. I believe the update is made atomic to the web app: http://code.google.com/apis/gears/api_localserver.html That is correct. Gears starts serving a manifest's resources only when everythin

Re: [whatwg] Google Gears and HTML5

On 5/31/07, Maciej Stachowiak <[EMAIL PROTECTED]> wrote: On May 30, 2007, at 8:32 PM, Robert O'Callahan wrote: On the plus side, JAR files make versioning and and consistency incredibly simple. It's not clear what the Gears ManagedStore does if it gets a 404 or some other error during an update

Re: [whatwg] Google Gears and HTML5

On May 30, 2007, at 8:32 PM, Robert O'Callahan wrote: I know Mozilla has considered other approaches to offline web apps, but I think the LocalServer type approach seems cleaner than Mozilla's JAR file plan, since it is much more transparent and allows local resource caching to be decoupled f

[whatwg] Google Gears and HTML5

*Maciej Stachowiak wrote:* Now that Google Gears has been announced, I'd like to see the features in it added to the HTML5 spec, since these are features that should ultimately be a part of basic web technology, not an extension. Agreed... Ian has already added a S

[whatwg] Google Gears and HTML5

Hey Everyone, Now that Google Gears has been announced, I'd like to see the features in it added to the HTML5 spec, since these are features that should ultimately be a part of basic web technology, not an extension. Ian has already added a SQL API which is fun