这是一个观察者设计模式的实现。
正如我们所看到的模型视图关系是间接的观察者设计模式为基础。
As we have seen, the Model-View relationship is an indirect one based on the Observer design pattern.
在设计控件与服务引擎时更加注重他们的独立性架构，充分利用观察者设计模式，使得项目具有灵活的扩展性。
Taking into account independence between modules for further extension, this project makes full use of the observation pattern in control and service engines design.
这种方法有稍些不同，因为它以设计者正积极与模式目录互动并使用模式间的关系作为前提的。
This approach is slightly different, because it assumes that the designer works actively with design pattern catalogs and USES the relationships between those patterns.
另一方面，软件服务和数据设计和分析，通常是由那些暴露于存储库和并行开发模式下的建模者来执行。
Software service and data design and analysis, on the other hand, is generally performed by modelers who have been exposed to repositories and the usual parallel development pattern.
RDBMS设计者的精力主要集中于优化I/O和设法用驱动器的块结构来安排数据访问模式。
RDBMS designers concentrated on optimizing I/O and tried to align the data access patterns with the block structure imposed by the drives.
设计者使用集成开发环境(IDE)来产出设计并为服务供应发布一个服务描述(WSDL)和服务产品的模式。
A designer USES an Integrated Development Environment (IDE) product to design and publish a service description (WSDL) and schemas for a service offering.
但是……应用flyweight [g oF]模式给设计者带来了新的挑战。
But... applying the Flyweight [GoF] pattern raises a new challenge for our designer.
一旦模型被校准，测试者将会看到另一组图片。在解释说明了作为结果的神经模式后，研究人员设计的程序会从六百万张图像中挑选出相应的图像。
Once the model was calibrated, the test subjects looked at another set of pictures.
本文中，您将会看到模式设计者如何克服障碍实现该功能。
In this article, you see how schema designers overcome barriers to enable this functionality.
如果您希望了解如何重用其他模式设计者的经验，那么也会受益于这篇教程。
You can also benefit from this tutorial if you want to learn how to reuse the experience of other schema designers.
随着世界从以生产为中心的行业模式转向以消费者需求为中心的行业模式，设计和创意变得更加重要。
As the world moves from a production-centric model of industry to one focused on consumer requirements, design and creativity become ever more important.
如果您是一名程序员，并且是设计模式的爱好者，我保证您会发现反模式能够提供的不止这些。
If you're a programmer and a fan of design patterns, I am sure that you will find that antipatterns have much to offer.
这种模式是让设计者集中于设计应用程序的显示部分，而开发者则集中于开发驱动应用程序功能所需的组件。
This pattern allows designers to concentrate on the display portion of an application and developers to concentrate on developing the components required to drive the application's functions.
大多数AOP实践者目前用现有的AOP支持实现事务和授权功能，通常是通过使用方面继承的设计模式。
Most AOP practitioners are currently implementing transactional and authorization concerns with existing AOP support, typically through the use of design patterns utilizing aspect inheritance.
没什么具体的模式——软件架构师、项目经理、程序员、DBA、业务分析师、UI设计者等等——因此该系列并不会按照这种方式来组织。
There is no overarching scheme of gaps to fill out – software architect, project manager, programmer, DBA, business analyst, UI designer, etc. – so the series is not preplanned in that sense.
几年来，开发者已经发布了很多关于设计模式描述很深入的书和文章，但有关反模式的相同社区却少之又少。
Developers have published insightful books and articles on design patterns for years, but the same community has been conspicuously less forthcoming on antipatterns.
即使没有其他内容，这次讨论也突现了这一事实，考虑API消费者的使用模式在确定合适设计的过程中扮演了举重轻重的角色。
If nothing else, the discussion has highlighted the fact that consideration of the usage patterns of API consumers plays a large part in determining an appropriate design.
因此，模型应以这样一种方式建立：产生的XML模式能够被协调以准确的建立设计者的心中所想。
So the model has to be created in such a way that the generated XML Schema can be tuned to create exactly what the designer had in mind.
我的目标就是提供一个简单、直接的设计模式的集合，作为请求-响应模型替代者。
My goal is to present a collection of simple, straightforward design alternatives to the request-response model.
如果没有正确的SOAP消息设计，则可能无法正确交换xml有效负载，即使有效负载遵循提供者和使用者的公共XML模式也是如此。
Without a correct design of a SOAP message, an XML payload may not be exchanged properly even if the payload follows a common XML schema for both providers and consumers.
在为数据服务消费者设计WSDL契约时，需要导入模式，其目的是为了让WSDL文档和被用来实现数据编配的接口保持一致。
When designing WSDL contracts for data service consumers, schemas need to be imported in order for the WSDL documents to be consistent with the interfaces used to implement the data orchestration.
SOA需要技术多面手：开发者和设计者必须精通消息传递标准和消息传递模式、XML技术、SOA平台和工具。
SOA requires knowledgeable technical staff - Developers and designers need to be proficient with messaging standards and messaging patterns, XML technologies, SOA platforms and tools.
有经验的模式设计者最终可以使用模式引擎的高级特性将类扩展至多个位置。
Experienced pattern designers may eventually be able to use advanced features of the pattern engine to expand classes into multiple locations.
XML模式设计者和实现人员需要一种方法来扩展现有的枚举列表。
XML schema designers and implementers need a way to extend existing enumerated lists.
当时的大会挤满了学习对象、设计模式和设计技术的开发者们。
Conferences were filled with developers learning about objects, design patterns, and design techniques.
对OOP特性的了解还让PHP编码者得以利用设计模式—一些众所周知的用来解决常见问题的算法。
Access to OOP features also allows PHP coders to leverage design patterns - well-known algorithms used to solve commonly occurring problems.
紧急设计的一个主要推动者是发现和积累惯用模式的能力：在代码库中大量重复的流程、结构和惯例。
One of the primary enablers of emergent design is the ability to see and harvest idiomatic patterns: processes, structures, and idioms that repeat in nontrivial ways within your code base.
这些指导原则可以使模式设计者找到实用的最佳实践，而且可以帮助他们创建易于实现、可扩展的枚举列表。
These guidelines can empower schema designers with real-world, practical best practices and can help create easy-to-implement, extensible enumerated lists.
模式设计者和实现人员需要一种扩展XML模式中现有枚举列表的方法。
Schema designers and implementers need a way to extend existing enumerated lists in XML schema.
应用推荐