This is an important aspect of the services pattern I talked about earlier, as well as of the forms designer.
这是我在前面讨论的服务模式以及窗体设计器的一个重要方面。
The Pattern solution implementation contains services, components, and other software artifacts, which implement the patterns, guided by the recipe.
模式解决方案实现包含服务、组件和其他软件构件，用于根据菜谱实现模式。
This pattern employs a common registry so that the services are visible throughout the enterprise.
此模式使用一个公共注册中心，因此服务在整个企业中可视。
Depending on the number of components and services we want to generate, we may need to create many more pattern bindings.
我们也许需要创建更多的模式绑定，这取决于我们想生成的组件和服务的数量。
A company that wishes to offer services consistently, regardless of location, may adopt this pattern.
希望提供一致服务(而不考虑位置)的公司可以采用此模式。
This makes it possible to use this metadata to classify, store, and retrieve many kinds of package assets, including components, services, pattern implementations, templates, and so on.
这就使得有可能使用这种元数据对多种资产包--包括部件、服务、实现模式、模板等--进行分类，储存和追溯。
Some generated services that use an adapter will never have an adapter pattern.
有些生成的服务使用了适配器却从不使用适配器模式。
This particular pattern recipe USES SOA patterns to implement and optimize services.
这个特殊的模式菜谱使用SOA模式实现和优化服务。
Finally, lazy acquisition pattern was applied to the initialization of services by exposing a startup method with the framework context interface.
最后，利用框架上下文接口公开一个启动方法，从而将延迟获取模式应用在服务的初始化中。
Additionally, because the design-time infrastructure is built on top of the service pattern I discussed earlier, debugging services can be a problem.
另外，因为设计时基础结构是在我前面讨论的服务模式之上生成的，所以调试服务可能会成为一个问题。
This pattern supports the virtualization of services in the following manner: To invoke another business unit's services, you define a service stub on the local ESB, encapsulating the registry lookup.
这种模式通过以下方式来支持服务可视化：为了调用另一个业务单元的服务，在本地es b上定义了一个服务存根来封装注册中心查找。
You can use this simple pattern to load plug-ins and provide services to plug-ins (such as logging and configuration).
您可以使用这种简单的模式来加载插件，以及向插件提供服务(例如，日志记录和配置)。
Service portals typify this pattern, providing a single point of contact for multiple services and hiding the details of internal services.
服务门户是此类模式的代表，它为多个服务提供单一联系点，并隐藏内部服务的细节。
This feature can be used to support a services gateway pattern.
可以使用此功能来支持服务网关模式。
The examples are based on a service gateway pattern, a powerful pattern with respect to mediation policies for target services.
这些示例基于服务网关模式，该模式是一种与目标服务中介策略相关的功能强大的模式。
Single Global Companies generally choose a matching SOA pattern in which services are specified and owned by the entire organization.
单一的国际化公司通常选择一种匹配的SOA模式，在这种模式中，服务是由整个组织指定和拥有的。
It also is extensible to integrate with backend services either via API or any other integration pattern like ESB etc.
它也是可扩展的，可以通过API或任何其他集成模式(如esb)集成后端服务。
Message exchange pattern: data services could be accessed via the four primary message exchange patterns - request/reply (tight SLA), request/reply (relaxed SLA), fire/forget, and publish/subscribe.
消息交换模式：数据服务可以通过四种主要的消息交换模式被访问：请求-应答（严格SLA）、请求-应答（宽松SLA ），即发即弃和发布-订阅。
This pattern essentially aligns your services with business activities.
这个模式实际上是让服务与企业活动保持一致。
One of the main advantages of the gateway pattern is that it allows for services to be offered over protocols that they were not originally designed for.
网关模式最主要的优点之一是，它允许服务以未经设计的协议来提供。
Because the executor pattern encapsulated execution for all services, a common exception-handling strategy was applied to all services.
因为执行程序模式将所有服务的执行封装了起来，所以可以将一个通用的异常处理策略应用于所有服务。
Support for Services Gateway pattern.
对服务网关模式的支持。
This strategy uses the pattern "A" illustrated in Figure 3 - Using Web Services Gateway.
该策略使用了图3（使用Web服务网关）中的模式A。
Implementation of a command pattern with Web services, where a SOAP message defines the command and attachments contained in supporting XML documents.
Web服务的命令模式的实现，SOAP消息在此定义了命令及附件，它们被包含在支持的XML文档中。
The pipeline pattern is used to "pipe" an incoming message to several services.
管线(pipeline)模式被用来将一条传入消息“输送”给几个服务。
The book discusses the Model-View-Controller pattern, unit testing, Web services, security, and many other topics that are critical to building effective Web applications.
该书讨论了Model -View - Controller模式、单元测试、Web服务，安全性和对有效的Web应用程序的构建起关键作用的许多其他主题。
It is the Observer pattern on top of the base web services infrastructure that gives DEBA its callback capability.
在基本Web服务结构之上采用观察者模式，就为DEBA带来了回调能力。
It's a better idea to base a web services solution on the MVC pattern.
在MVC模式基础上来实现Web服务解决方案会更好点。
RPC-style Web services generally follow the same basic implementation pattern.
rpc样式的Web服务通常都采用相同的基本实现模式。
RPC-style Web services use the same synchronous request-response pattern that is typically seen in OO-style object method invocations.
RPC 样式的Web服务使用了在 OO 样式的对象方法调用中常见的同步请求-响应模式。
应用推荐