On 20.11.2012 13:33, Mariano Martinez Peck wrote:
And why it is a AppRegistry. AppRegistry
associates some application, tool. It is very confusing to
use it for
a sound provider.
More the name of AppRegistry being confusing, what it does is
provide infrastructure for registering providers of a service, and
switching which is currently in use.
In other words, SoundService (due to being an ApprRegistry) can
switch between using multiple SoundSystems.
Would it make sense to rename AppRegistry to ServiceRegistry therefore?
In my mind it would at least. :)
That or ServiceProvider, depending on whether one feels the focus should
be on its role in registering multiple implementors, or its role in
accessing/using those implementors.
Cheers,
Henry
