BinaryTreeComponentName

 ComponentName

 DefaultNamingSubSystem Default implementation. Keeps services map as a simple hash table. Keeps key map as a list dictionary to maintain order. Does not support a query string.

 KeySearchNamingSubSystem When requesting a component by service, KeySearchNamingSubSystem first determines if more than one component has been registered for that service. If not, Default resolution occurs. If so, all of the registered keys for that service are processed through the provided Predicate to determine which key to use for service resolution. If no Predicate matches, the default resolution occurs.

 NamingPartsSubSystem Alternative implementation. Extends the default implementation replacing the key support with a more complete ComponentName. Supports queries.

 INamingSubSystem Contract for SubSystem that wishes to keep and coordinate component registration.