locator
n. 定位器,探测器
2026-04-13 16:04 浏览次数 18
n. 定位器,探测器
uniform resource locator[计] 统一资源定位符
ultrasonic locator超声波定位器
cable locator电缆探测器
sound locator[声]
point locator探穴仪
electroacoustic locator电声异物定位器
Model Locator模型定位器
metal locator[电子] 金属位置器;金属探寻器
bullet locator弹片探测器
This is simple to apply to an existing application: just change the service locator implementation to disable or remove the cache.
将其应用于现有应用程序很简单:只要改变服务定位器实现去禁止或去除缓存。
The first component to move towards the service locator design, and away from its singleton origins, is the one that depends on no other singletons, yet may be depended by other singletons.
迈向服务定位器设计、摆脱单件血统的第一个组件是不依赖于其它单件、但被其它单件依赖的组件。
A singleton service locator with a resource cache creates a global cache that cannot properly handle the component-level mappings for an overloaded resource name.
带有资源缓存的集合服务定位器创建全局缓存,通过这种方式不能为重载的资源名正确处理组件级映射。
When two components use a resource name that is overloaded — that is, a name that is bound to two different resources — a caching service locator returns the same resource to both components.
当两个组件使用一个重载的资源名,也就是说,一个名称绑定到两个不同的资源,缓存服务定位器为两个组件返回相同的资源。
Business logic code that USES a service locator avoids becoming cluttered with directory lookup code, and so is easier to understand.
业务逻辑代码使用服务定位器避免目录查找代码变得混乱,因此它很容易理解。
But the service locator should not include a resource cache.
但是服务定位器不应包含资源缓存。
The service locator skips the JNDI lookup and USES the resource from the cache instead.
服务定位器略过JNDI查找并取而代之的使用缓存中的资源。
The client passes in a unique identifier — a resource name — for the resource; the service locator finds the resource and returns it to the client.
客户端为资源传递一个唯一的标识符(资源名),服务定位器找到这个资源并把它返回给客户端。
My third implementation used a service locator with no cache.
我的第三个实现使用没有缓存的服务定位器。
Then DB2 opens the cursor returns from the procedure and processes the locator allocation to the result set.
然后,DB2打开从过程中返回的游标,并处理分配给结果集的定位器。
Therefore, J2EE 1.3 applications should not include the resource cache in their service locator implementations.
因此,在J2EE 1.3应用程序中,服务定位器的实现不应该包含资源缓存。
Service locator implementations usually include a resource cache to avoid repeated lookups of the same resource.
服务定位器实现通常包括资源缓存,以此来避免对相同资源的重复查找。
Just as predicted, overloaded resource names and a caching service locator makes the code execute differently; it makes some components get the wrong resources.
正如所预测的那样,重载的资源名和缓存服务定位器使得代码执行有不同的结果,它使某些组件取得错误的资源。
This is because the service locator will cache the resource for whichever component USES the overloaded name first.
这是因为服务定位器将缓存不论哪个组件首次使用时所重载的名称的资源。
Do not just assume that a caching service locator significantly improves application performance; use performance testing to confirm that it does.
不要只假设缓存服务定位器能显着的提高应用程序的性能,要使用性能测试来证明这一点。
OK, so a caching service locator causes errors for overloaded resource names.
好,既然是由于缓存服务定位器导致重载资源名时的错误。
Wherever there are singleton lookup in the legacy codebase, a small change is made to lookup the same component via the service locator instead.
凡是在遗留代码集中出现单件查找的地方,稍加修改即可换用服务定位器来查找同样的组件。
Since the service locator is basically stateless, multiple components sharing the same instance is not a problem.
由于服务定位器基本上是无状态的,所以多个组件共享相同实例是没有问题的。
This single value is a locator to the transition table, which the procedure USES to access the transition table columns.
这个单值是转换表的定位器,存储过程用它来访问转换表的列。
In general, choose familiar locator expressions and be consistent in script structure.
一般来说,选用熟悉的定位器表达式,并在脚本结构中保持一致。
To make this safe, you need to have a mechanism to lock the service locator and make it read only.
为了安全,你需要用一种机制来锁定服务定位器并使之只读。
We have seen that an overloaded resource name and the typical service locator implementation, a singleton with a resource cache, do not get along.
我们已经看到了重载资源名和典型服务定位器实现,有资源缓存的集合,但他们之间并没有很好的合作。