Transports

In Ice terminology, a transport is a conduit for exchanging Ice protocol messages. Ice supports a number of transports; some of them are built into the Ice core, while others are available as plug-ins. Your transport selection will be driven by application requirements. For example, the TCP transport might be acceptable for deployment on a trusted intranet, while an Internet-facing application will generally use SSL or WSS (WebSocket Secure).

Most transports have a configuration component, which is often done statically via the application's external configuration file. Some transports also provide an API for accessing special features programmatically. Finally, certain Ice features might not be available with all transports. For example, you can send oneway invocations with any transport, whereas twoway invocations require a stream-oriented transport and datagram invocations require the UDP transport.

You'll need to choose a transport as soon as you're ready to test your first client-server prototype, if not sooner. The server's object adapter and the client's proxy must have at least one matching endpoint, where an endpoint is simply a transport name together with any necessary options. Ice uses a simple text-based syntax for configuring endpoints.

All of Ice's IP-based transports support both IPv4 and IPv6, as long as the underlying platform also supports both. You can set configuration properties to enable or disable them, and control whether IPv4 or IPv6 has priority.

The following table summarizes the transports that Ice provides and indicates whether they are built into the Ice core in C++, C#, Java, and indirectly in the C++-based implementations:

Ice for JavaScript supports a different set of transports: