The reason for having a separate interface class for the media player is to allow for new players to be registered in the future. The service presents a binder interface to the client, and then instantiates the correct player type based on the client request. This model will be extended to the media recorder and metadata retriever classes.
On Dec 22, 5:53 pm, hanchao3c <[email protected]> wrote: > Got it . > Current: > MediaMetadataRetrieverInterface.h > MediaPlayerInterface.h > and in the future > MediaRecorderInterface.h > > It seem the XXXXInterface is interface for impl. > > In Current mediaplayer: > IMediaPlayer is the Client of MeidaPlayerService . > mediaplayer.c call it. > > If mediarecord will not using client-service. > Is IMediaRecorder.h useless ? > > On 12月23日, 上午6时56分, Dave Sparks <[email protected]> wrote: > > > No, but there will be a MediaRecorderInterface.h class that it > > inherits from in the future. > > > On Dec 22, 1:58 am, hanchao3c <[email protected]> wrote: > > > > The Class PVMediaRecorder in PVMediaRecorder.h seems similar to the > > > Metadata Retrieve. > > > But this class hasn't inherited any class. > > > > Should they inherit IMediaRecorder (in IMediaRecorder.h ) to give a > > > same interface > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
