在轴心点实现高速缓存系统将其与服务代码分离开来。
Implementing the caching system at the pivot point isolates it from the service code.
模板层背后的思想就是表示层代码与业务层代码分离。
The idea behind the Template layer is that the presentation layer code is separate from the business-layer code.
如果你在做快速原型开发，不需要总是使用“代码分离”技术。
If you are doing quick prototyping, there is no need to always use the "code behind" technique.
与应用代码分离的资源，它能让你的应用通过各种设备配置优雅的优化其行为。
Resources that are separate from the application code and allow your application to gracefully optimize its behavior for a variety of device configurations.
如你所见，使用“代码分离”方法，你的代码会非常简明而易于维护。
As you can see, by using the "code behind" approach, your code is very concise and maintainable.
这个练习的目标是将高速缓存与实际的Web服务代码分离开来。
The goal in this exercise is to isolate the cache from the actual web service code.
通过代码分离技术三种方法的介绍和比较，解决了现存的代码混乱问题。
This paper solves the question of code mixed through introducing and analyzing three methods about code separation technique.
将该部分代码分离成它自己的包，并避免必须为该小代码部分创建单独的存储库。
You can always separate that part of the code later into a package of it's own, and avoid having to create a separate repository for that small code part.
如果换用接口来表示Customerpersistence类，可以实现一些代码分离。
You can achieve some code separation if you represent the concrete Customer Persistence class as an interface instead.
使用二级ajax控制器(如servlet或Web服务)可以进行更强大的模型代码分离。
Having a secondary Ajax controller (such as a servlet or Web service) forces a stronger separation of your model code.
异常处理机制是一种运行时错误通知机制，将程序的正常控制代码和错误处理代码分离。
Exception handling is a runtime-error notifying mechanism. It separates the error handling code from normal code and makes software do its utmost to run on the normal state.
基础设施功能(如安全、事务和可靠消息传递的使用)都是采用声明方式处理的，已从实现代码分离。
Infrastructure capabilities, such as Security, Transactions and the use of Reliable Messaging are also handled declaratively and are separated from the implementation code.
若文档与代码分离，那么每次改变代码后都要改变文档，这无疑会变成相当麻烦的一件事情。
If the documentation and the code are separate, it becomes a hassle to change the documentation every time you change the code.
安全透明度可将作为应用程序的一部分运行的代码与作为基础结构的一部分运行的代码分离。
Security transparency separates code that runs as part of the application from code that runs as part of the infrastructure.
JiBX使用与源代码分离的绑定定义，要求每个想包含到XML表示中的项目要显式地在绑定中命名。
JiBX USES binding definitions which are separate from the source code, and requires each item to be included in an XML representation to be explicitly named in the binding.
外部化的业务规则：mdi中的规则引擎已与操作代码分离，可提供灵活性，能在无需重新编码的情况下针对新业务情况进行调整。
Externalized business rules: rules engine in the MDI is separated from operational code, for increased flexibility to adjust to new business conditions without recoding.
注意到，代码为每个环境使用三个分离的数据库。
Notice that the code USES three separate databases for each environment.
在使用PHP的情况下，如果页面标记和代码能够分离将是十分理想的。
In the case of PHP, it would be ideal if page markup and code could be segregated.
这种方法提供了文件格式库和应用程序代码之间某种程度上的分离。
This method gives you some degree of separation between a file format library and your application code.
这种类型的设计的好处是很明显的。同样，遵循角色分离、代码重用等也是非常有益的。
The benefits to this type of design should be obvious, and follow along the lines of separation of roles, reuse of code, and so on.
该层的作用在于针对不同的数据存储技术，从业务逻辑中分离数据访问代码。
The power of this layer is in separating data access code from the business logic for disparate data store technologies.
面向资源计算的核心是将信息（资源）的逻辑请求与传递请求的物理机制（代码）相分离。
The core of resource oriented computing is the separation of logical requests for information (resources) from the physical mechanism (code) which delivers it.
面向资源计算的核心是将信息(资源)的逻辑请求从发送请求的物理机制(代码)中分离出来。
The core of resource-oriented computing is the separation of logical requests for information (resources) from the physical mechanism (code) which delivers the requests.
通常，在您计划如何为被测试应用的特性和行为进行分离和组织测试代码时，您将会使用关注分离这个基本原理。
Typically, you will use the separation of concerns principle when you plan how you will divide and structure your test code for application-under-test features and behaviors.
应当重构代码以分离各个应用层。
You should refactor the code to separate the various application layers.
不能将数据库选择与连接之后编写的代码完全分离。
You can't totally separate your choice of database from the code you write after you've connected.
以这种方式分离您的代码将产生一个组织良好的代码结构，使得诊断和修复可能出现的问题要容易得多。
Separating your code in this manner will lead to a highly organized code structure, making it far easier to diagnose and fix any problems that may arise.
通过使用装饰模式，实现执行调用的代码与提供缓存的代码相分离，将非常简单。
By using the Decorator pattern, it is simple to separate the code that performs invocations from the code that provides caching itself.
通过直接在CLI上运行脚本，可以轻松地分离出代码中存在的问题。
The problem with the code can be easily isolated by running the script directly on the CLI. Run
通过直接在CLI上运行脚本，可以轻松地分离出代码中存在的问题。
The problem with the code can be easily isolated by running the script directly on the CLI. Run
应用推荐