Hi stefan,
There are two ways for synchronisation in Google Doc (http://
code.google.com/apis/gears/architecture.html).
I 'll be place a icon button on page ,like google reader offline
icon button, then the user can judge whether online or offline.
if there are validation errors or conflicting changes to data in
background when you sync data between server and local database, we
can display workerpool message to page.
sorry for my poor english .
Alex
On Mar 11, 6:16 pm, stefan <[email protected]> wrote:
> Hi 浩翔,
>
> looks similar to what i got here. the main thing is, i think that the
> client is writing to the local-db all time in both modes.
> You decided for a user driven data - synchronisation. Personally i
> think it is better, to directly confront the user with the
> data - synchronisation situation instead of background syncing. In
> case of validation errors or conflicting changes to data, it is more
> understandable to the user what is happening. The more i think about;
> it also could be possible that users don't know if they are off or on.
> why did you decided for manual driven data - synchronisation?
>
> On 11 Mrz., 07:52, 浩翔 <[email protected]> wrote:
>
> > Hi all,
>
> > This is the architecture of my offline web application , I need
> > some suggest.
>
> > http://4.bp.blogspot.com/_6lbO8zu9hgg/SbdP-g1gCjI/AAAAAAAAACs/-4I6OCs...
>
> > Thank you !
>
> > Alex
