您要查找的是不是:
- Loose coupling has many advantages. 松散耦合有许多优点。
- Is your definition of loose coupling too tight? 您对松散耦合的定义是否太过狭窄呢?
- Loosely coupled is almost always better. 松耦合总是更好一些。
- Can serialize most objects, but the result is not loosely coupled. 可以序列化大多数对象,但结果不是松耦合的。
- Is the routine loosely coupled with the rest of the code? 函数是否和其他代码松耦合?
- Loosely coupled, extensible database access library written in C#. 这是用C%23编写的松散耦合的、可扩展的数据库访问类。
- Distribution is based on the concept of loosely coupled nodes. 分布式是基于松散耦合节点的概念之上的。
- Strive for loosely coupled designs between objects that interact. 为了交互对象之间的松耦合设计而努力!
- Remote system call mechanism is presented in this paper, which can reorganize the loose coupled operating system functions and then provide some complete standard API to support representative applications. 我们提出了一种远程系统调用机制,它能重组松散耦合的操作系统功能,并利用这些功能提供完备的标准程序接口,从而支持典型应用;
- Is a service that allows for a loose coupling of events between components. 是允许在组件之间使用松耦合的事件的服务。
- UDDI not only structurally fits the needs of loose coupled knowledge services system, but also technically fits the characteristics of distributed heterogeneous knowledge services network. UDDI不仅在结构上适应松耦合的知识服务系统的要求,而且在技术上也适应知识服务网络的分布性及异构性特点。
- Support lightweight programming models that allow for loosely coupled systems. 支持允许松散连接系统的轻量级程序模式。
- As a result, application code written using Spring AOP is loosely coupled. 所以,用Spring AOP编写的应用程序代码是松散耦合的。
- The best choice is to design a loosely coupled system based on services. 最佳选择就是设计一种松散耦合的基于服务的系统。
- Web service abstraction layer, loose coupling, and XML based format are susceptible to performance constraints. Web服务抽象层、松散耦合和基于XML的格式易受到性能限制的影响。
- But we have heard that service-oriented architecture is all about loose coupling. 但我们曾听说服务导向的架构都是与松散耦合有关的。
- It also matches the loose coupling that is often characteristic of large human organizations. 这种做法也适合于松散耦合,而松散耦合常常是大型组织的特征。
- Interfaces and loose couplings are very venerable software engineering concepts, but this Enterprise Service Bus, I think, is a key enabler. 接口和松散耦合是两个由来已久的软件工程概念,但是我认为企业服务总线是使这个概念成为可能的关键因素。
- This loose coupling is mandatory in environments where the simultaneous updating of all parties in the message exchange is not possible. 在不可能同时更新消息交换中所有方的环境中,这种松耦合是强制的。
- Service-oriented architectures alleviate that problem by providing what is called "loose coupling," shown here via the double-headed black arrows. 面向服务的架构通过提供所谓的“松散耦合”减轻了这个问题,在图中由黑色双箭头指示。