MVC is all about proper separation of concerns.
MVC最重要的就是合理的分离关注点。
This is called, in a loose sense, a separation of concerns.
这在松散意义上称为关注点分离。
A key characteristic of an ESB is separation of concerns.
ESB的关键特性是分离关注点。
Remember that separation of concerns thing mentioned earlier?
还记得早先提到的关注分离吗？
This is another example of the separation of concerns in JSF.
这是在JSF中分离关注点的另一个例子。
Keep separation of concerns by separating the interfaces from each other.
通过相互分离接口保持关注点的分离。
Finally, delegating logic often leads to a cleaner separation of concerns.
最后，委派逻辑通常会得到更干净的关注点分离。
It also allows for an improved separation of concerns in the finished system.
它还允许在最终完成的系统中实现更好的关注分离。
Such USES of the Template Method pattern offer good separation of concerns.
模板方法模式的这种用法提供了关注点的好的分离。
This tutorial will demonstrate two implementations of this separation of concerns.
这篇教程将展示关注点分离的两个实现。
By nature, the MVC pattern is highly testable and encourages good separation of concerns.
MVC模式天生就是可测试的，而且鼓励对关注点的分离。
One of the goals of leveraging an Enterprise Service Bus (ESB) is separation of concerns.
利用企业服务总线(Enterprise Service Bus,ESB)的目标之一是关注事项分离。
Achieve a clear separation of concerns between architectural building block responsibilities.
在架构构建块职责之间可以实现一个清晰的关注点分离。
Respecting separation of concerns, even if initial size of the two concerns is rather unequal.
注重关注点分离，即使两个关注点的初始大小差别很大。
For example, suppose you know that you want the separation of concerns of Model-View-Presenter.
例如，假定您知道需要分离模型-视图-表示器(Model - View -Presenter)关注点。
But that is the whole point of separation of concerns that we have discussed throughout these columns.
但它是分离关注点的关键，我们在这些专栏中讨论过这个问题。
Through separation of concerns, integration requirements are decomposed into more granular services.
通过关注点分离，可以将集成需求分解为更细粒度的服务。
It is designed to create a separation of concerns between application protocols and security protocols.
它用于创建应用程序协议和安全协议之间的分离关系。
As a result, the concept of separation of concerns is the foundation to the definition of the integration services.
因此，关注点分离的概念是定义集成服务的基础。
This separation of concerns means you can change one component with zero to minimal impact on other components.
采用关注点分隔原则意味着，对一个组件的修改对其他组件的影响非常小，甚至没有影响。
In these cases, web services are developed without any regard to the concepts of layering and separation of concerns.
在这些情况下，Web服务是在不考虑任何分层和分离概念的情况下开发的。
It enhances our ability to express the separation of concerns necessary for a well-designed, maintainable software system.
它提高了我们对于一个设计良好的、可维护的软件系统所需的、关注点分离的表达能力。
Part 2 introduced the ID-lists pattern to reduce the number of remote calls and still obey the separation of concerns pattern.
第2部分介绍了利用ID - lists模式减少远程调用的数量，并且还遵守分离关注点模式。
The three primary goals of MDA are portability, interoperability, and reusability through architectural separation of concerns.
MDA的三个首要目标就是通过关注点的架构分离的可移植性、互操作性和可重用性。
Hyperspaces goes beyond the encapsulation of crosscutting concerns and attempts to manage multi-dimensional separation of concerns.
Hyperspaces超越了对横切关系的封装，并尝试管理关系的多维分离。
Apache Cocoon: Download and get more information on this Web development framework built around the concepts of separation of concerns.
ApacheCocoon：下载此框架并了解这个围绕关注分离概念构建的Web开发框架的更多信息。
The architecture itself serves as the primary vehicle for dividing the application into structures that reflect a separation of concerns.
体系结构本身充当将应用程序划分为反映关注分离的结构的主要机制。
Explicit separation of concerns between implementation of the service functionality (business logic) and enterprise data support logic.
服务功能(业务逻辑)的实现和企业数据支持逻辑的实现在关系上的明确分离。
When you're aiming for separation of concerns, transparency, and flexibility, aspect-oriented programming (AOP) is often the right answer.
如果目的是分离关注点、透明性和灵活性，那么面向方面的编程 (AOP)通常就是正确的答案。
Figure 1 illustrates the separation of concerns concept by showing the flow of code between the development workstation to final production.
图1显示了开发工作站和最终生产环境之间的代码流，我们以此来说明关注点分离的概念。
应用推荐