The component interaction of the system defined by this architecture is illustrated in Figure 4.
这个架构定义的系统的组件交互在图 4 中展示。
A full description with a complete and detailed component descriptions followed by component interaction walkthroughs can be found in the Resources section.
在参考资料中可以找到完整的描述、对组件的详细描述和组件交互演示。
Interaction patterns — component interaction patterns help solve design problems related to collaboration, communication, and coordination of components of the architecture.
交互模式——组件交互模式可帮助解决与体系结构的组件的协作、通信及协调相关的设计问题。
It enables service providers and service consumers to work with dynamic component interactions to construct interaction models that exploit the flexibility and power of this model.
它使服务提供者和服务消费者能够使用动态组件交互来构建交互模型，这些交互模型能够利用该开发模型灵活性和强大功能。
The other patterns include support for a subset of the component and module interaction types.
其他模式则包括针对组件和模块交互类型的子集的支持。
They have interaction points that allow connections to other domains, but in the most flexible design these are established at application assembly time and not at the component design stage.
它们具有交互点，可以通过交互点连接到其他领域；但是，在最灵活的设计中，这些交互是在组装应用程序时而不是在组件设计阶段确定的。
Other component teams that have a closer interaction with the application layer may need to collaborate more closely with feature teams in order to understand their requirements.
有时候需要另外一些与应用层有密切互动的组件团队来与特性团队更紧密地合作，以理解他们的需求。
All key events are discarded until user interaction or code explicitly sets focus ownership to a particular component.
直到用户交互或代码明确地设置了焦点所有权为特殊的组件，才丢弃所有的键事件。
The runtime framework controls communication between components and provides runtime support for the interaction manager, delivery context, and data component.
运行时框架控制组件间的通信，并提供对交互管理器、交付上下文和数据组件的运行时支持。
The desire to mediate the interaction of two components is often more easily accomplished in fine-grained components by directly modifying the component implementations or configurations.
在细粒度组件中，通常可以直接修改组件实现或配置，从而更为方便地通过中介传递两个组件间的交互。
When the calling component is a long running process, the preferred interaction style is always honored.
当调用组件是长时间运行的进程时，将始终采用首选交互样式的设置。
All customer interaction is through this port, thereby separating customer clients from interactions that the component might have with other service consumers or providers.
所有的客户之间的交互都是通过这个端口进行的，因此将客户与构件可能与其他服务客户或者提供商之间的交互隔离开来。
If the component is enabled to work using either direct action or user interaction, then that decision can be left up to the application assembler.
如果组件能够通过直接操作或用户交互而工作，那么可以由应用程序装配程序作出决策。
The interaction manager sends and receives all messages between the runtime framework and the modality components, and queries and updates the data component as needed.
交互管理器负责发送和接收运行时框架和通道组件间的所有消息，查询和更新所需的数据组件。
When the calling component is a short running process, the preferred interaction style is honored for one-way target operations.
调用组件是短时间运行的进程时，将对单向目标操作采用首选交互样式。
If the calling component (or source) initiates the interaction synchronously, SCA will switch the interaction to be asynchronous.
如果调用组件(或源)以同步方式发起了交互，sca会将此交互切换为异步方式。
A service provided by a separate software component is unavailable for a certain time period, and the service implementation has to be taken over by manual interaction.
某个单独的软件组件提供的服务在某个时段内不可用，并且服务实现必须通过手动交互接管。
The low-level communication protocols used to facilitate interaction between the browser and the server-side component are hidden behind the API.
用来处理浏览器和服务器端组件间的交互的低层通信协议都藏于 API 之后。
It lets you decouple the invocation pattern used by the interaction between client and service provider from the sync-only invocation pattern used by component test.
它允许您将客户端和服务提供程序之间的交互所使用的调用模式与组件测试所使用的仅同步调用模式分离开。
Because any server interaction is local to each component and separate from the inter-script communication, cookies are not exposed.
由于任何服务器交互都在每个组件本地并且与脚本间通信分离，因此不会暴露cookie。
You do not need to know any of the particulars about the component implementations - all interaction with them will be through their RESTful HTTP interfaces.
您无需知道任何有关组件实现的详情—所有与它们的交互都通过其RESTfulHTTP接口来实现。
BPEL provides human task component for the human interaction with the business process.
BPEL为业务流程中的人机交互提供了Human任务组件。
WebSphere Integration Developer provides a human task component, which greatly simplifies the work required to support human interaction with an SCA application.
WebSphereIntegrationDeveloper提供了一个人工任务组件，可以极大地简化支持人与SCA应用程序交互所需要的工作。
Regardless of the selected channel interaction, the associated channel interface component would use SOAP messaging to communicate with MAM Services.
不管选择了何种通道交互作用，相关联的ChannelInterface组件都将会使用SOAP消息传递来与 MAM 服务通信。
The Gwittir project is a component library for GWT, with an emphasis on using a consistent UI to model interaction scheme. The authors of Gwitter describe it in this way.
Gwittir项目是GWT的一个组件库，它的重点在于使用一个一致的用户界面对交互机制建模。
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)。
For each component type, there may be multiple properties that you need to set; for example, the Preferred Interaction Style on the target component interface is one of these properties.
对于每个组件类型，可能会需要设置多个属性；例如，目标组件接口上的PreferredInteractionStyle就是需要设置的属性之一。
In this option, a fifth component, called the Controller, is added for performing interaction orchestration between the four core components and to provide user interface with an external client.
在这个选项中，添加了第5个组件Controller来执行4个核心组件之间的协调，同时为用户接口提供一个外部客户端。
In general, when considering an interaction from one component (source or client) to another (target), the service client determines what type of invocation will be used.
通常，当考虑从一个组件(源或客户端)到另一个组件(目标)的交互时，服务客户端将确定使用哪种类型的调用。
In general, when considering an interaction from one component (source or client) to another (target), the service client determines what type of invocation will be used.
通常，当考虑从一个组件(源或客户端)到另一个组件(目标)的交互时，服务客户端将确定使用哪种类型的调用。
应用推荐