On Tue, Mar 3, 2009 at 8:13 AM, meerkat <[email protected]> wrote:
> Hi,
>
> I mean insert the data from the server db to the local db that Gears is
> using.

You can do that so long as the main page is up and running. If the
user chooses to 'quit the app', it stops happening.

>
> meerkat
>
>
>
>
>
> From: [email protected] [mailto:[email protected]] On
> Behalf Of Dinh Ba Thanh
> Sent: Tuesday, March 03, 2009 9:37 AM
> To: [email protected]
> Subject: [gears-users] Re: workers
>
>
>
> What do you mean by background sync? From what I understand, workerpool API
> only can do background work if you stay on the page. As soon as you move to
> another page/reload the page, the workers stop.
>
> Best Regards,
>
> Dinh Ba Thanh, Jason
>
> [email protected]
>
>
>
>
>
>
>
>
>
> On Mar 3, 2009, at 5:36 PM, meerkat wrote:
>
>
> Thanks for that.
>
> How do you do background syncs then of data on a page?
> meerkat
>
>
>
> -----Original Message-----
>
> From: [email protected] [mailto:[email protected]]
>
> On Behalf Of Michael Nordman
>
> Sent: Tuesday, March 03, 2009 1:10 AM
>
> To: [email protected]
>
> Subject: [gears-users] Re: workers
>
>
>
>
>
> On Mon, Mar 2, 2009 at 4:54 PM, meerkat <[email protected]> wrote:
>
>
>
> Hello,
>
> I have a series of workers inserting data from a mysql db(via JSON)
>
> into the gears sqlite db. This works fine when the user is online and
>
> remains on the calling page.
>
>
>
> Do the workers continue, once they have been instantiated, even if the
>
> user moves away from the htm page on which they were started?
>
>
>
> Workers shutdown once their containing page goes away.
>
>
>
>
>
> I am trying to work out how to do one way background syncs of data
>
> from server to the local db without user intervention.
>
>
>
> Insights welcome.
>
> Meerkat
>
>
>
>
>
>

Reply via email to