Why the dalvik VM does not simplify the serialization mechanism to use the same implementation as Parcelable ? Using Parcelable is not convenient compared to Serializable (just have to implement it and specify which fields are transient), is there a reason to keep Serializable as slow as J2SE ?
On Nov 24, 1:36 am, "Dianne Hackborn" <[EMAIL PROTECTED]> wrote: > We generally avoid Serializable because it has a significant amount of > overhead. > > On Sun, Nov 23, 2008 at 5:38 AM, Huebi <[EMAIL PROTECTED]>wrote: > > > > > I was wondering why data classes like Address or GeoPoint do not > > implement Serializable but only Parcelable. I'd like to store these > > into a file which does not seem to be possible. I can use Preferences > > instead, making it a data container, which is surely not what it is > > intended to be used for. So any reasons why Serializable is not > > implemented? > > -- > Dianne Hackborn > Android framework engineer > [EMAIL PROTECTED] > > Note: please don't send private questions to me, as I don't have time to > provide private support. All such questions should be posted on public > forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
