On Wed, Jun 5, 2013 at 10: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. > > So, I guess technically that is a change in semantics--so it wouldn't > be like "oh, your GWT app fails to compile", more like "you were doing > *what* with that field...that doesn't work anymore". Or we're exposing > a value over the wire that previously the developer knowingly made > final so that it would not (seems pretty odd though...). Yes, that is what we were worried about -- particularly that some Google internal app was putting some sensitive data in final fields and previous scrutiny didn't uncover it because it didn't go over the wire. Then, making final fields serializable would essentially be a leak of sensitive information. > > I think we will at least want a flag to turn it on and > > off. It might be temporary just to land the patch; not sure if it > > should survive until the 2.6 release. > > Okay, well, technically a flag for that already exists in the patch--I > suppose we could land it as is and then hope to maybe remove it by 2.6 > or there after. I was just hoping to simplify it. > > I'll plan to move it over to gerrit then... Does having the flag really make it that much more complicated? -- John A. Tamplin -- 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.
