---
title: "Locators"
url: https://docs.zeroc.com/ice/3.8/runtime/locators
docs_index: https://docs.zeroc.com/llms.txt
---

> For an index of every page, see [llms.txt](https://docs.zeroc.com/llms.txt).

# Locators

In [Terminology](https://docs.zeroc.com/ice/3.8/basics/terminology.md), we described briefly how the Ice runtime uses an intermediary, known as a *location service*, to convert the symbolic information in an indirect proxy into an endpoint that it can use to communicate with a server. This section expands on that introduction to explain in more detail how the Ice runtime interacts with a location service. You can create your own location service or you can use [IceDiscovery](https://docs.zeroc.com/ice/3.8/plugins/icediscovery.md) or [IceGrid](https://docs.zeroc.com/ice/3.8/services/icegrid.md), which are both implementations of a location service. Describing how to implement a location service is outside the scope of this documentation.

A *locator* is an Ice object that is implemented by a location service. A locator object must support the Slice interface `Ice::Locator`, which defines operations that satisfy the location requirements of the Ice runtime. Applications do not normally use these operations directly, but the locator object may support an implementation-specific interface derived from `Ice::Locator` that provides additional functionality. For example, IceGrid's locator object provides access to an `IceGrid::Query` object so that applications can perform [more sophisticated queries](https://docs.zeroc.com/ice/3.8/services/icegrid/well-known-objects.md).

## See Also

- [Terminology](https://docs.zeroc.com/ice/3.8/basics/terminology.md)
- [IceDiscovery](https://docs.zeroc.com/ice/3.8/plugins/icediscovery.md)
- [IceGrid](https://docs.zeroc.com/ice/3.8/services/icegrid.md)
- [Querying Well-Known Objects](https://docs.zeroc.com/ice/3.8/services/icegrid/well-known-objects.md)
