John Wang wrote:
This has been gone back and forth on this thread already. Again, I agree it is not the perfect solution. I am comparing that to the current behavior, I don't think it is worse. (Only in my opinion).
So, if it's good enough for you, a user of java serialization, then perhaps those of us who don't use java serialization shouldn't complain. I think we'd want to add to the documentation something to the effect that this is all that's been done, and that if the classes change substantially then all bets are off. We do not want to imply that we're making any cross-version compatibility guarantees about serialization, rather just that folks who're willing to take their chances will not be impeded. Could something like that work?
Doug --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
