On Mon, Jul 27, 2009 at 9:24 PM, Dianne Hackborn <[email protected]> wrote: > On Mon, Jul 27, 2009 at 8:35 PM, rukiman <[email protected]> wrote: >> Yes I did mean Java serialization. Any reason why I can't use it >> (apart from it being slow) ? > > Um... it being super-crazy slow? :)
It's also very fragile, in that small innocuous-seeming changes to your code could subtly break your serialization, and, worse, small innocuous-seeming changes to the platform code could also break it. We on the Android team of course endeavor not to break application code, but we are not perfect by any stretch of the imagination, and serialization is a known tricky area to get right. Personally, I might use serialization when prototyping a system, but I would be very reluctant to include its use in a finished product. All that being said, if you happen to profile your serialization-using code and find that the slowness is directly due to code in the core library (classes in java.*, javax.*, or org.apache.*), I would appreciate a bug report detailing your observations. Cheers, -dan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" 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/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
