Parcelable CharSequence vs Serializable String (Worth it? Measurements?)

Asked Dec 19 '17 at 04:17

Active Dec 19 '17 at 04:23

Viewed 217 times

While digging through the JDK docs, I noticed that String in Java SE implements Serializable. With that in mind, I now assume that Strings (when used with Intents and Bundles) go to the destination through Serializable.

My question is mainly: Is a CharSequence subclass that implements Parcelable worth it? Does it have performance improvements? If so, can I measure this? I am currently working with an app that has a lot of Strings (some Strings large themselves for parsing).

edited Dec 19 '17 at 04:23

asked Dec 19 '17 at 04:17

ReverseEffect

I get that generally, the data transfer is faster when using Parcelable. I'm talking explicitly about implementing CharSequence. – ReverseEffect Dec 19 '17 at 04:21
`String` is a special case in Serialization. It is normally implemented via `DataOutput.writeUTF().` I doubt that you can improve on it. – user207421 Dec 19 '17 at 04:28
Interesting. Are there any other exceptions to Serializable? – ReverseEffect Dec 19 '17 at 04:29
Several: `Class`, arrays, `ObjectStreamClass`. – user207421 Dec 19 '17 at 06:24

Parcelable CharSequence vs Serializable String (Worth it? Measurements?)

0 Answers0