Figure 3 shows the contexts supported by component configurator.
图3显示了由组件配置器实现支持的上下文。
Contexts supported by Component Configurator implementation.
由组件配置器实现支持的上下文。
Component configurator provided a dynamic mechanism for managing service life cycle and deployment.
组件配置器提供了一套动态机制，用来管理服务生命周期和部署。
The component configurator role was later expanded to provide for the discovery and management of the connections between services.
稍后，组件配置器的角色会得到扩展，以发现和管理服务间的连接。
The component configurator implementation was modified to implement a service context interface that was passed to services using their initialization method.
组件配置器实现经过修改，以实现一个服务上下文接口，使用服务的初始化方法，可以把上下文接口传递到这些服务。
The interaction between the explicit interface, proxy, invoker, and component configurator implementations relied heavily on C++ Run-Time Type Information (RTTI).
这个方法的重要后果是显而易见的。显式接口、代理、调用程序和组件配置器实现间的交互严重依赖于 C++实时类型信息 (Run-Time Type Information,RTTI)。
The team thought that the base classes would prove useful at a later point in the project when dynamic management of interceptors was envisaged, potentially with a component configurator.
团队认为，稍后在项目中，当设计出拦截器的动态管理时(可能是使用组件配置器设计的)，基类的作用将被证实。
Two sources were consulted during discovery: the local "repository" of services, which was managed by the component configurator implementation, and a "service registry" in a well-known location.
在发现期间查询了两个来源：由组件配置器实现进行管理的本地服务“存储库”，以及位于一个已知位置的“服务注册中心”。
Two sources were consulted during discovery: the local "repository" of services, which was managed by the component configurator implementation, and a "service registry" in a well-known location.
在发现期间查询了两个来源：由组件配置器实现进行管理的本地服务“存储库”，以及位于一个已知位置的“服务注册中心”。
应用推荐