通过相互分离接口保持关注点的分离。
Keep separation of concerns by separating the interfaces from each other.
经过良好定义的分离接口是由显式接口引入的，它能创建用来管理和测试的通用接口，服务可以按照要求提供支持。
The well-defined, decoupled interfaces introduced by explicit interface enabled the creation of general purpose interfaces for management and testing, which services were able to support as required.
它为函数库服务分离了接口和具体实现。
It separates the interface and implementation for the library services.
WSDL通过提供包含这些信息的不同元素来支持接口和实现的分离。
WSDL supports the separation of interface and implementation by providing different elements that contain this information.
最初它主要是作为一种分离用户接口逻辑与业务逻辑的策略被设计出来的。
It was primarily devised as a strategy for separating user interface logic from business logic.
例如，从服务的角度来看，灵活性(及其“姊妹概念”重用)是通过将接口与实现及具体协议绑定分离来实现的。
For example, from a services Angle, flexibility (and its "sister," reuse) is gained through separation of the interface from implementation and from binding to specific protocols.
分离API和SPI接口的目的在于保护来源于程序提供者的应用程序，以便达到可移植性。
The intent of separating the API and SPI interfaces is to shield applications from the provider so that portability can be achieved.
SOA要求服务松耦合，服务间的接口是固定的，且与实现相分离。
SOA demands loose coupling of services, where the interface is fixed and separate from the implementation.
保证稳定的服务接口和易变的不稳定服务实现的分离。
Enable separation between stable service interfaces and possibly volatile and unreliable service implementations.
由于使用了接口分离特定的运营系统，因此应该在业务规划方面具有更大的灵活性。
The use of interfaces to isolate specific operational systems should provide greater flexibility in business planning.
此技术将每个EIS与服务器分离开来，因为只有资源适配器需要理解EIS接口和连接问题。
This technique decouples each EIS from the server, because only the resource adapter needs to understand the EIS interface and connectivity issues.
因为应用程序使用无状态的服务接口，所以此时的课程实例看作已经与持久化上下文 “分离”。
Because the application uses a stateless service interface, the course instance is at this point considered "detatched" from the persistence context.
此层通过将点对点连接与接口本身分离，从而对服务实现虚拟化。
This layer virtualizes the services by decoupling the point-to-point connections from the interfaces themselves.
生成实现类所在的包与生成接口所在的包是相分离的。
The implementation classes are generated in a package separate from the one in which the interfaces are generated.
此层通过将点对点连接与接口本身分离，从而将服务虚拟化。
It virtualizes the services by decoupling the point-to-point connections from the interfaces themselves.
使用生成存根的应用程序可以利用抽象服务接口，并且这样与协议和WSIF客户机api分离。
Applications that use the generated stubs can use the abstract service interface and are thus insulated from the protocol and the WSIF client API.
显式模式接口与实现的分离。
如果换用接口来表示Customerpersistence类，可以实现一些代码分离。
You can achieve some code separation if you represent the concrete Customer Persistence class as an interface instead.
它拥有对于其消耗的供应产品(offering)的运行时接口，而非编译时接口，并且只对使用的供应产品(offering)中的客户有效(换句话说，分离时它不是有效的)。
It has a run-time interface, not a compile time interface, to its consuming offering, and is only available to customers in a consuming offering (that is, it is not available separately).
例如，我们可能会添加想与模型分离开来的用户接口逻辑，或者我们可能会出于性能方面的原因而添加某些类。
For example, we might add user interface logic that we want to keep separate from our model, or we might add some classes for performance reasons.
服务接口放在第三方代理中，这有助于您更好地管理接口，并支持更快速和更灵活的应用程序耦合和分离。
The service interfaces are put into a third-party broker, which helps you manage the interfaces better, and enables faster and more flexible coupling and decoupling of applications.
由显式接口和查询提供的服务透明性，可以在服务和服务间的接口之间进行分离。
Service transparency was provided by explicit interface and lookup, which provided decoupling between services and the interfaces between them.
分离的上下文接口将上下文实现和上下文用户分离开来。
Decoupled context interface provided a decoupling between context implementation and context user.
我们已经了解到，要对软件进行恰当设计，以将流程序列逻辑、策略、基本计算、人机接口和数据管理分离开来。
We've learned to design software to separate process sequencing logic, policy, basic computation, human interface, and data management.
如果接口和实现被清楚地分离和保护，你就可以轻松地完成它，你要做的只是重新连接一下你的新库。
If the interface and implementation are clearly separated and protected, you can accomplish this and require only a relink by the user.
构造了一个程序设计与知识库相分离的通用的数据库自然语言接口系统模型。
A universal system model about database natural language interface, which separates the programming from Knowledge-Base is constructed.
将核心编辑应用单独分离出来，提供协同文本编辑的功能并对外部提供访问核心编辑功能的接口。这样一方面是系统结构清晰，另一方面对于系统功能的扩充也大有裨益。
To separate the nuclear editing application and provide the access interface, it makes the system structure clear, on the other hand, it is beneficial to the extension of the system functionality.
委托和接口都允许类设计器分离类型声明和实现。
Both delegates and interfaces enable a class designer to separate type declarations and implementation.
委托和接口都允许类设计器分离类型声明和实现。
Both delegates and interfaces enable a class designer to separate type declarations and implementation.
应用推荐