Default INamingSubSystem implementation. Keeps services and key maps as simple hash tables. Does not support a query string.

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.

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