Well, i think i figured it out. You have to initialize the local server on
every page and initialize the managed store...beyond that I think it's set?
On Feb 3, 2011, at 4:17 PM, Kevin Layman wrote:
> On second thought though, if you do not have a single entry point to your
> multipage app (like a sign on page?) you will have to include the Gears init
> code on any page that a user may be able to access directly via an url.
>
>
> On Thu, Feb 3, 2011 at 4:22 PM, Kevin Layman <kevin.lay...@gmail.com> wrote:
> I believe that Gears is going to want to install once for your domain and
> after that anything under that domain should be good to go.
>
>
> On Thu, Feb 3, 2011 at 3:42 PM, Brian Campbell
> <brian.campb...@nursinghomequality.com> wrote:
> It's not an option. I have to support IE browsers and of course there's no
> appcache support in IE prior to V9.0...and it will probably be another decade
> before our clients upgrade...
>
>
> On Feb 3, 2011, at 2:38 PM, Michael Nordman wrote:
>
> > Gears has been deprecated. I'd recommend looking into the
> > offline/storage related features in HTML5 instead of Gears.
> >
> > On Thu, Feb 3, 2011 at 9:56 AM, bcamp1973
> > <brian.campb...@nursinghomequality.com> wrote:
> >> Assuming a client with offline support, my assumption is to do the
> >> following on EVERY page of the application?
> >>
> >> // Check for gears of course
> >> if (!window.google || !google.gears) {
> >> location.href = "http://gears.google.com/?
> >> action=install&message=<your welcome message>&return=<your website
> >> url>";
> >> }
> >>
> >> // Initialize local server and check for manifest update
> >> var localServer = google.gears.factory.create('beta.localserver');
> >> var store = localServer.createManagedStore('myManagedStoreName');
> >> store.manifestUrl = 'myManifestFileName.json';
> >> store.checkForUpdate();
> >>
> >> // Optionally initialize DB if needed on per page basis
> >> var db = google.gears.factory.create('beta.database');
> >> db.open('myDatabaseName');
> >> // do db stuff
> >> rs.close();
> >>
> >> Is this correct? The documentation seems pretty thorough, but wasn't
> >> sure what's a one-time thing and what needs to be addressed on every
> >> page session. This is my first attempt at an offline client so I'm not
> >> used to dealing with persistence without pulling from the server ;)
> >>
>
>
>
