---
title: "Connection Management"
url: https://docs.zeroc.com/ice/3.8/runtime/connection-management
docs_index: https://docs.zeroc.com/llms.txt
---

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

# Connection Management

An Ice communicator establishes connections automatically and transparently as a side effect of using proxies. There are well-defined rules that determine when a [new connection is established](https://docs.zeroc.com/ice/3.8/runtime/connection-management/connection-establishment.md) and when [connections are closed](https://docs.zeroc.com/ice/3.8/runtime/connection-management/connection-closure.md).

Connection management becomes increasingly important as network environments grow more complex. In particular, if you need to make callbacks from a server to a client through a firewall, you must use a [bidirectional connection](https://docs.zeroc.com/ice/3.8/runtime/connection-management/bidirectional-connections.md). In most cases, you can use a [Glacier2 router](https://docs.zeroc.com/ice/3.8/services/glacier2.md) to automatically take advantage of bidirectional connections. However, the Ice API also provides direct access to connections, allowing you to explicitly control establishment and closure of both unidirectional and bidirectional connections.

> **Note**
>
> The discussion that follows assumes that you are familiar with [proxies](https://docs.zeroc.com/ice/3.8/runtime/invocation.md) and [endpoints](https://docs.zeroc.com/ice/3.8/runtime/invocation/proxy-endpoints.md).

## Topics

- [Connection Establishment](https://docs.zeroc.com/ice/3.8/runtime/connection-management/connection-establishment.md)
- [Connection Closure](https://docs.zeroc.com/ice/3.8/runtime/connection-management/connection-closure.md)
- [Bidirectional Connections](https://docs.zeroc.com/ice/3.8/runtime/connection-management/bidirectional-connections.md)
