On Tuesday, October 9, 2012 9:03:35 AM UTC+2, Christoph Henrici wrote: > > Best thanx. Szenario 1, would mean that you have to deal with two > different sets of data structures online = entityproxies and offline > something else..... or you have to develop your "own" layer above request > factory.... which to avoid was the rational behind using requestfactory. > > Szenario 2 seems like a interesting approach, but i must confess i not > knowlegable enough of the internals of Requestfactory to really be able to > see what that means. >
Have a look at http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/web/bindery/requestfactory/shared/ProxySerializer.html but beware that there are issues with it (known and probably unknown too). > Also for adressing the issue with the potential confict resolution this is > probably not the "right" layer.... > > So probably you need something above RequestfFactory, which deals with a > "higher level" batching and offline / online awareness etc....... > Synchronization (and conflict resolution) is hard. In the end, it's probably easier to either use the "last write wins" (possibly at the property level rather than object level; that would make it more of less equivalent to OT) or to simply store duplicates and then provide a mean to reconcile/merge data. It seems to be more or less what Google does for the contacts for instance. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/QSyF8AbQwpUJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
