AIDL and Fragments

Catherine is out of town, so it’s just me and the cat.  I’m trying to catch up on Fragments, AIDL and the Android Security model.

AIDL bumps into some serious problems when combined with design for inheritance.  I think the best idea is an abstract base class whose unmarshaller, the reference stored in the public CREATOR member, is a factory for all of the subtypes.

I suppose you could do it like JDBC did: each subclass registers, in a static initializer, with the base class.  Nah… that’s a bad idea.

About bmeike
Android developer and evangelist in Oakland, CA

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: