You might have to do the following: 1. Use local server module to capture the static urls which could be accessed when not connected 2. Store the data using the Database module 3. You could use the Worker Pool module to effeciently handle resource intense operations 4. As Michael pointed out you might have to handle your client in offline and online mode. When not connected you should store the action locally and when connected you might have to synchronize both online and offline changes.
Useful tips could be found @ http://code.google.com/apis/gears/architecture.html Srikanth On Feb 26, 12:00 am, Michael Nordman <[email protected]> wrote: > There is no easy answer to this question. The level of effort required > really depends on the application in question. In general, apps that > are heavily dependent on server-based dynamic page generation (.jsp > .asp) are more difficult to "take offline" compared to more AJAX heavy > apps that programmatically construct the HTML DOM. > > On Wed, Feb 25, 2009 at 2:11 AM, coolguy <[email protected]> wrote: > > > I was going through some gears presentations and articles and found it > > really impressive... > > > I haven't tried any working example of gears but would like to know > > how easy is it, to make an existing web based application, available > > for off line use with gears. do i need to invest significant effort to > > redo my web app??to make it work with gears? > > > sahil
