OTOH, I have to agree, that avoiding serialization as described in your link is best. But if you really do need serialization, if you really cannot get buy with Mark's idea of using the SQL database instead, if even the Parcelable interface is not good enough for you, then instead of using XML, you should consider JSON. But you can substitute JSON for XML only if you do not need the semantic info that XML conveys.
In fact, that is one of the things that people forget when using JSON. When the server code changes, you now need to redo the client code that relies on this semantics -- since it is not in the JSON. But JSON is so lightweight, it is tempting. On Feb 18, 10:33 am, Streets Of Boston <[email protected]> wrote: > The answer is; not necessarily. > It is best described > here:http://stackoverflow.com/questions/2917847/serialization-performance-... > > In other words: Don't serialize. > > Another reason is that it's relatively slow on Android. Use the Parcelable > interface instead. -- 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
