描述显式接口实现的准则。
Describes guidelines for explicit interface implementations.
它还能确保代理和调用程序对象与显式接口的特定远程实现没有关联。
It also helped to ensure that proxy and invoker objects were not associated with particular remote implementations of explicit interfaces.
该方法能保证服务客户机对实现其调用的显式接口的具体服务不具有依赖性。
The approach ensured that service clients had no dependencies on the concrete services that implemented the explicit interfaces they invoked.
下列设计准则有助于确保您的库设计仅在需要时使用显式接口实现。
The following design guidelines help ensure that your library design USES explicit interface implementation only when appropriate.
由显式接口和查询提供的服务透明性，可以在服务和服务间的接口之间进行分离。
Service transparency was provided by explicit interface and lookup, which provided decoupling between services and the interfaces between them.
通知事件通过回调型显式接口以及与之对应的代理和调用程序对象，与观察器进行通信。
Notification events were communicated to observers with call-back explicit interfaces and their respective proxy and invoker objects.
如果在本地存储库中找到了一个支持所需的显式接口的服务，将返回对该服务对象的直接引用。
If a service supporting the required explicit interface was found in the local repository, a direct reference to the service object would be returned.
服务上下文提供了本地和远程两种方式，用来发现为所需的显式接口提供支持的服务。
The service context provided both local and remote discovery of services supporting required explicit interfaces.
“服务生成器”的功能是根据显式接口为代理、调用程序和服务类生成框架代码，它已经被部分编写出来。
A partial "service Generator" was written that generated skeleton code for proxy, invoker, and service classes from an explicit interface.
该模式的应用是在客户机-服务器引入的异步行为以及显式接口引入的各个接口的基础上构建的。
The application of this pattern built upon the asynchronous behavior introduced by client-server, and the interfaces introduced by explicit interface.
显式接口实现还允许程序员实现具有相同成员名称的两个接口，并为每个接口成员各提供一个实现。
Explicit interface implementation also allows the programmer to implement two interfaces that have the same member names and give each interface member a separate implementation.
是利用经过良好定义的接口从服务提供者的细节中抽象出来的，这些接口由显式接口以及代理和调用程序对象提供支持。
Ed from service provider details with well-defined interfaces supported by explicit interfaces, and proxy and invoker objects.
经过良好定义的分离接口是由显式接口引入的，它能创建用来管理和测试的通用接口，服务可以按照要求提供支持。
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.
使用纯粹的抽象 C++显式接口类与真正的服务调用透明性是矛盾的，因为非 C++系统中的服务客户机需要备用的接口定义。
The use of pure abstract C++ explicit interface classes worked against true service invocation transparency, because service clients on non-C++ systems required alternative interface definitions.
不幸的是，此假设与实际不符，因为在元数据级别上位于每个接口上的每个方法都有各自的槽(slot)(这使得显式接口实现得以工作)。
Unfortunately, it is incompatible because at the metadata level every method on every interface has its own slot (which makes explicit interface implementations work).
这个方法的重要后果是显而易见的。显式接口、代理、调用程序和组件配置器实现间的交互严重依赖于 C++实时类型信息 (Run-Time Type Information,RTTI)。
The interaction between the explicit interface, proxy, invoker, and component configurator implementations relied heavily on C++ Run-Time Type Information (RTTI).
匿名类是一种语法速写标记，使您能够在需要实现某个抽象类或者接口的地方创建一个类的实例，而不需要显式提供类的名称。
An anonymous class is a kind of syntactic shorthand that lets you instantiate a class implementing an abstract class or interface where you need it, without having to explicitly give it a class name.
利用显式的与实现无关的接口来定义服务。
The use of explicit implementation-independent interfaces to define services.
当组件接口包括能够使消息进行相互关联的数据时，就出现了显式相关性。
Explicit correlation occurs when the component interface includes business data that can be used to correlate messages.
此时，对设计人员来说，C11、C12和C13是体系结构构造(或组件)；其中每个构造具有显式定义的外部接口。
At this point, to this designer, C11, C12, and C13 are architectural constructs (or components); each of them has explicitly defined external interfaces.
显式地指定接口似乎有点限制，且在重命名接口或将接口迁移到另一个程序包时需要更改xml。
Specifying the interface explicitly might seem a bit constraining and lead to the need to change the XML when the interface is renamed or moved to another package.
完成一个事务的时间（以毫秒计）在单节点上是：常规锁——1877，显式写入锁——1225，而使用“脏接口”的话是181。
The time (microseconds) to perform the transaction for a single node were 1877 with regular locking, 1225 with an explicit write lock, and 181 using a "dirty interface".
List的源代码中真的显式声明了那么多接口吗？
Does the List source code actually state all those interfaces?
在开发时执行时，此过程与上面列出的第一个选项非常相似，我们在此选择中显式地选择Add类的Math接口实现。
When performed at development time, this process is very similar to the first option listed above in which we explicitly selected the Add class' implementation of the Math interface.
契约式设计的一个主要优势是，它在接口或类本身当中提供了关于预期行为的显式信息。
One of the major benefits of Design by Contract is that it provides explicit information within the interface or class itself about expected behavior.
规范因此描述了显式的服务上下文如何映射到服务的远程接口中，而隐式的上下文通常却不能这样做。
The specification then describes how explicit service contexts are mapped into the remote interface of a service, whereas implicit contexts are typically not.
它还定义了发布器注册接口(及方法)，以允许发布器显式地向代理注册自己。
It also defines a publisher registration interface (and methods), allowing a publisher to explicitly register itself with the broker.
良好的编程实践通常包括显式地定义已检查用户异常作为接口契约的一部分。
A good programming practice often involves explicitly defining checked user exceptions as part of the interface contract.
本地接口必须被您的应用程序显式地进行访问，这需要代码的改变和防止以后配置EJB时需要应用程序的改变。
Local interfaces must be explicitly called by your application, requiring code changes and preventing the ability to later distribute the EJB without application changes.
本地接口必须被您的应用程序显式地进行访问，这需要代码的改变和防止以后配置EJB时需要应用程序的改变。
Local interfaces must be explicitly called by your application, requiring code changes and preventing the ability to later distribute the EJB without application changes.
应用推荐