http://code.google.com/apis/gears/gears_faq.html#Best__PracticesTOC
Has some really good advice. Two that I'd highlight are: 1.) Wrap multiple inserts in a transaction. - The performance gains are pretty significant. 2.) Do database work in a worker and and only in one worker. - only doing db work in one worker eliminates the problem of not being able to open the db because another worker has it open. (and having to implement some crazy retry mechanism) rob On Mar 10, 2:21 pm, stefan <[email protected]> wrote: > Hi Community, > actually i am trying to get an existing, very data-heavy read/write > web application to work still online like before and partly offline > using gears. Now there are several ways getting this done. Gears is > new Technology, best practices are not available. I mean i didnt found > anything besides some "Hello Worlds". > At this time the only way i see is rewriting the client to the "data- > switch"-model from the > architecture guide. Is there a more easy way? > Is there someone out-there who already made an existing application > working with gears or knows what is best to do? > > Cheers > Stefan
