On Mon, Sep 26, 2011 at 7:38 PM, TreKing <treking...@gmail.com> wrote: >> Anyways, besides designing parcelable as a performance improvement over >> serializable I'm still puzzled by why the android team had to come up with >> both bundles and parcels and not just have say bundles. > > Good question. I'd love to hear on that as well.
That's akin to asking why we have java.util.List and java.util.ArrayList, and why we can't just have java.util.ArrayList. One (List) is the interface, and there can be many possible implementations of the interface. The other (ArrayList) is a very flexible and popular implementation of that interface. But there are other implementations of List with different characteristics, like Stack or CopyOnWriteArrayList. The OS uses Parcelable in many places. Parcelable *can* be used by SDK applications, but in a few spots (like the ones you've encountered) it causes problems, because the OS tries to reconstitute objects from parcels in places it arguably shouldn't. Why *that* is happening would be my question... -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Warescription: Three Android Books, Plus Updates, One Low Price! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
