Ben, Thanks for your answers. With regard to the last question I was trying to inquire about licensing schemes for applications built using gears.
If I want to charge for the use of an application is there any functionality within gears that supports that process? I guess I could just build the security into the web site - and gears would have no part in the process. I was just wondering how best to deliver a chargeable application built with gears. On Sep 24, 3:14 pm, "Ben Lisbakken" <[EMAIL PROTECTED]> wrote: > On Wed, Sep 24, 2008 at 4:38 AM, dkrumholz > <[EMAIL PROTECTED]>wrote: > > > > > Just getting started with Gears, I have some conceptual questions - > > > 1. If I have an offline database and add a parent record with a db > > generated key and then child records with that key - how does the > > server db prevent collisions between my keys and another user's > > offline keys? > > DB generated keys should never be the same so I don't think you would run > into this problem. If you are creating your own keys, then you should make > sure you never use an existing keys. > > > > > 2. What is the best way to allow a limited number of users (some not > > all) to share data? Do I need to rely on server data and build the > > user access requirements into the app? > > Yes, that is correct. > > > > > 3. What is the best method to grant and restrict access that allows > > for licensing of apps? > > What exactly are you trying to accomplish? If you want to restrict access > to shared data or restrict the ability to synchronize data for offline > usage, the code should be implemented on the serverside such that when a > user tries to sync they will send a request to sync and the server will > validate/respond with data or invalidate/respond with a denial. > > -Ben
