As with most Sametime services, the directory lookup service operates in an asynchronous manner.
与大多数Sametime服务类似，目录查询服务以异步方式运作。
Business logic code that USES a service locator avoids becoming cluttered with directory lookup code, and so is easier to understand.
业务逻辑代码使用服务定位器避免目录查找代码变得混乱，因此它很容易理解。
The game workload is much more like Lightweight Directory Access Protocol (LDAP) or telephony directory lookup: lots and lots of small transactions over simple tables.
游戏的负载更接近于 LightweightDirectoryAccessProtocol（LDAP）或电话簿查询：对简单的表执行大量的小事务。
Subsequent calls to the service get the security of password authentication without actually having to incur the overhead of a database connection or corporate LDAP directory lookup.
对这个服务的后继调用可以获得密码认证的安全性，而实际上不一定会导致数据库连接或公司LDAP目录查找的开销。
In contrast, Lightweight Directory Access Protocol (LDAP) repositories are service-oriented; only specific lookup APIs are provided.
相反，轻量级目录访问协议(Light weight Directory Access Protocol,LDAP)存储库是面向服务的，仅提供了特定的查找api。
For demonstrating the function of the Partner Lookup plug-in, you need to populate the LDAP directory with some sample data.
为了演示PartnerLookup插件的功能，需要使用一些样例数据填充ldap目录。
The service Locator pattern (see resources) is a well-known J2EE application design pattern that encapsulates the code needed to lookup resources through directory services such as JNDI.
ServiceLocator模式(参见参考资料)是J2EE应用程序中著名的设计模式，它封装了需要通过目录服务(如JNDI)查找资源的代码。
In order for the partner Lookup plug-in to gather information about a particular Sametime partner, that partner must exist in the LDAP directory.
为了使PartnerLookup插件收集关于特定Sametime合作伙伴的信息，该合作伙伴必须存在于LDAP目录中。
Portal passes the LtpaToken to the Domino Web Access server, which does a lookup in the Domino directory for uid=jb013,ou=secret,dc=spies,dc=com.
门户传送 LtpaToken到DominoWebAccess服务器，Domino Web Access 服务器在 Domino目录中查找uid=jb013,ou=secret,dc=spies,dc=com。
This variable allows access to name lookup views in the Domino Directory during the view index process.
这个变量允许在视图索引过程中访问DominoDirectory中的名称查询视图。
The above configuration specifies the initial context factory as com.sun.jndi.fscontext.RefFSContextFactory and the provider URL as the file-based file:/C:/JNDI-Directory for JNDI lookup.
以上配置进行JNDI 查询时用 com.sun.jndi.fscontext.RefFSContextFactory指定初始上下文工厂，用基于文件的 file:/C:/JNDI-Directory作为提供者URL。
Performed by breaking the path into component names and performing a separate NFS lookup call for every pair of component name and directory vnode.
通过把路径放入部件名字实现和为每对部件名和目录节点分开的NFS查找调用来完成。
Sometimes it was just a matter of integrating new databases, such as adding a phone number and address lookup and a business directory.
有时只是合并新数据库的问题，如添加电话号码、地址查询以及企业目录。
Sometimes it was just a matter of integrating new databases, such as adding a phone number and address lookup and a business directory.
有时只是合并新数据库的问题，如添加电话号码、地址查询以及企业目录。
应用推荐