I won't be losing any sleep over it. Our data object structure is pretty robust, so it would be highly unlikely that it would be able to become invalid. Also, I'd be surprised if the RPC serialization occurred in anything but the current JS thread of execution. So I'd be a stunned mullet if we ran into trouble.
Having said that, I totally agree, it would be nice to know more about how the serialization works. On Mar 29, 1:52 am, martin liste larsson <[email protected]> wrote: > On Mon, Mar 28, 2011 at 4:41 AM, Craig Mitchell <[email protected]> wrote: > > FYI: The project I'm on will also be saving in the background. > > However, we will just transfer all the data back to the server on save > > (there really isn't that much), so I don't have to worry about the > > object statuses on the client (the server can work them out). > > Thanks for the info. > It seems you might get partially updated objects to the server then? > If it is possible for the user to modify the objects in the client > while the RPC- > code is serializing, I mean. > > IOW. if I can run into trouble, so can you. > > Or maybe there is no problem? Would be nice to know for sure ... > > M. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. 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.
