The mapping between of AOs onto different threads is a design choice. There is a cost to introducing an additional thread boundaries (i.e., mutex lock operations for shared data and additional thread context switches) so it's definitely not the case that the preference would be for each AO to go in its own thread. However, there are cases where it does make sense to have a thread boundary such as to decouple timing and it can be introduced in those cases. The integration of the Openmax codecs is one example where this was done. Anyway, I definitely do view the AO model as a limitation since it certainly does not prevent the introduction of thread boundaries. Instead it provides a framework for encapsulating independent but cooperating objects to run in the same thread.
On Dec 15, 10:18 am, Dave Sparks <[email protected]> wrote: > Packet Video developed OpenCore long before Android existed. I can't > speak for PV, but I think some design decisions would have been made > differently if the code was developed specifically for Android. > > On Dec 14, 11:26 pm, jasperr <[email protected]> wrote: > > > Does it mean by defualt, all AO(Active Objects) share a single > > pthread? > > > Why android prefer this over let each AO having its own thread? Or > > this is decision left to the platform developers? > > > In addition, how to configure this? Many thanks! > > > Best Regards > > Japserr --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" 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-framework?hl=en -~----------~----~----~----~------~----~------~--~---
