Figure 6 depicts this architecture.
图6描绘了此体系结构。
Figure 7.12 describes this architecture.
图12描述了这个架构。
This architecture conforms to the JSGI specification.
这个架构符合JSGI规范。
In this architecture, each server contributes equally.
在这种体系结构中，每个服务器的作用相同。
The Diagram below shows how this architecture would work.
下述图表展示了此架构是如何工作的。
This architecture is optimal for mobile web applications.
这种架构对于移动web应用程序而言是最优的。
Here are the basic functional units of this architecture.
以下是这种体系结构的基本功能单元。
Figure 1 shows the logical model view of this architecture.
图1显示了此体系结构的逻辑模型视图。
This completes the sample implementation of this architecture.
这样，该体系结构的样本实现就结束了。
There are a number of useful ways to visualise this architecture.
有很多有用的方法来形象表示该架构。
This architecture was chosen to optimize the archiving throughput.
这种架构被选来优化归档吞吐量。
This architecture is similar to a Web browser experience using Ajax.
该架构类似于使用 Ajax的Web浏览器体验。
To deploy to this architecture, no project Settings need to be changed.
部署这种体系结构不需要更改项目设置。
The two big ideas in this architecture are channels and bindings [...].
这种体系架构最突出的两个理念就是通道与绑定[…]。
This architecture includes a DMZ layer that protects the trusted network.
该体系结构包括一个dmz层，保护受信任的网络。
We're pleased to introduce this architecture improvement so that you can benefit.
我们很高兴引入了这个架构改进，让您能够受益。
This architecture spans a variety of technologies, specifications, and standards.
这个架构使用了多种技术、规范和标准。
This architecture is somewhat similar to the gateway as SSL endpoint architecture.
此体系结构部分类似于网关作为ssl端点的体系结构。
However, even in a best-case scenario, this architecture can cause deadlock issues.
然而，即使是在最好的情况下，这个架构仍然会引起死锁问题。
This architecture lets you decide at the time of deployment if you will use caching.
这个体系结构让您在部署时决定是否使用高速缓存。
Additionally, this architecture limits the security impact of any one of the components.
另外，这个体系限制了所有组件的安全影响。
This architecture is dynamically invoked using a static services mapping navigator file.
该体系结构是用静态服务映射导航文件来动态调用的。
This architecture allows applications to deal principally with data graphs and data objects.
此体系结构允许应用程序主要处理数据图和数据对象。
This architecture means that you can learn and use only the subset of UML that suits you best.
这样的架构意味着，你可以学习和使用UML那些最适合你的部分。
This architecture allows you to query ITM for historical data from a particular agent, if needed.
如果需要，该架构允许您从特定的代理查询ITM，得到历史数据。
The component interaction of the system defined by this architecture is illustrated in Figure 4.
这个架构定义的系统的组件交互在图 4 中展示。
This architecture can be applied for synchronous as well as asynchronous processing of SOAP messages.
这种体系结构可以应用于SOAP消息的同步处理和异步处理。
This architecture provides complete support for both synchronous and asynchronous messaging scenarios.
此体系结构提供了对同步消息传递和异步消息传递方案的全面支持。
In its most basic form, this architecture can be broken down into three tiers: front, mid, and database.
按照最基本的形式，这个体系结构可以分为三层：前端层、中间层和数据库层。
Of course, the most important benefit is that this architecture solves your reuse and EJB-REF problems.
当然，最大的益处是这个体系结构解决了您的重用及ejb - REF问题。
应用推荐