Your question make me think of OO database, you can make C/S both operate the database. Why bother to send the "CustomeData" back and forth .
在 2013年10月14日星期一UTC+8下午3时35分33秒，Richard Zhao写道： > > Hi there, > > I'm designing a client / service software. client / service are both on > some android. client and service communicate using messenger and data > format is class CustomeData. CustomeData also has some inner classes which > define detail structure. > > Do I need to make CustomeData as thin as possible? I intent to use it as > data format only recognized by both client and service. Service has > additional operations on CustomeData, and may store other info to it too, > for example _ID in DB. But client don't care what _ID is. > > I'm not sure whether I need to attach more operations on CustomeData or > create new objects in Service using CustomeData inner classes as a member. > > Thanks > Richard > -- 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 --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
