On Wed, Jun 5, 2013 at 7:46 PM, Stephen Haberman <[email protected]>wrote:
> > > I don't have a good idea about what could break > > I believe nothing would "break"--it's that final fields that were > previously not going over the wire would now go over the wire. > It's also possible that the newly exposed final field has a type that has a subclass that isn't designed for serialization. Or it might technically be serializable but actually sending it over the wire doesn't work right for whatever reason. Or perhaps it causes a GWT app's size to blow up because now we're trying to serialize the world. So yes, all sorts of things could go wrong, particularly in extremely complicated and buggy code like GWT-RPC. In principle, a refactoring of GWT-RPC to send some kind of context object all the way through seems like a good change since we might use it for other config settings. (Though it's probably something that we should land as a separate CL.) - Brian -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
