Yes, sure, with these semantics the names are right.

Ouf interest, what are the requirements for having the mechanism in that way? It seems more complex (all the reference counting, clients must not "forget" to release a service etc.) than a mechanism which just initializes a service upon first usage and closes it when e.g. the search factory is closed. Are there services which are started/stopped several times in the lifetime of one search factory? I'm just trying to understand the motivation for the current implementation a bit better.