John Wang wrote:
My proposal is to add the suid to Serializable classes
That's too brittle. If we do that, then what happens when we need to add a field to the class (eg, in 2.9 we've replaced "inclusive" in RangeQuery with "includeLower" and "includeUpper")? The standard answer is you bump the suid, but, then that breaks back compatibility. Since we would still sometimes, unpredictably, break back compatibility, no app could rely on it. You can't have a "mostly back compatible" promise. So... we have to either 1) only support "live serialization" and update the javadocs saying so, or 2) support full back compat of serialized classes and spell out the actual policy, make thorough tests for it, etc. Mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
