Internet Communications Engine

Short description: Open-source software

Internet Communications EngineDeveloper(s)| ZeroC

|

Stable release|

3.7.10 / November 7, 2023; 2 years ago (2023-11-07)

Platform| Cross-platform
Type| Remote procedure call framework
License| GPL / Proprietary
Website| zeroc.com

The Internet Communications Engine, or Ice, is an open-source RPC framework developed by ZeroC. It provides SDKs for C++, C#, Java, JavaScript, MATLAB, Objective-C, PHP, Python, Ruby and Swift, and can run on various operating systems, including Linux, Windows, macOS, iOS and Android.[1]

Ice implements a proprietary application layer communications protocol, called the Ice protocol, that can run over TCP, TLS, UDP, WebSocket and Bluetooth.[2][3] As its name indicates, Ice can be suitable for applications that communicate over the Internet, and includes functionality for traversing firewalls.

## Contents

* 1 History
* 2 Components
* 2.1 IceStorm
* 2.2 IceGrid
* 2.3 IcePatch
* 2.4 Glacier
* 2.5 IceBox
* 2.6 Slice
* 3 See also
* 4 Notes
* 5 External links

## History

Initially released in February 2003,[4] Ice was influenced by the Common Object Request Broker Architecture (CORBA) in its design, and indeed was created by several influential CORBA developers, including Michi Henning. However, according to ZeroC, it was smaller and less complex than CORBA because it was designed by a small group of experienced developers, instead of suffering from design by committee.[5]

In 2004, it was reported that a game called "Wish" by a company named Mutable Realms used Ice.[6] In 2008, it was reported that Big Bear Solar Observatory had used the software since 2005.[7] The source code repository for Ice is on GitHub since May 2015.[8]

## Components

Ice components include object-oriented remote-object-invocation, replication, grid-computing, failover, load-balancing, firewall-traversals and publish-subscribe services. To gain access to those services, applications are linked to a stub library or assembly, which is generated from a language-independent IDL-like syntax called slice.

### IceStorm

is an object-oriented publish-and-subscribe framework that also supports federation and quality-of-service. Unlike other publish-subscribe frameworks such as Tibco Software's Rendezvous or SmartSockets, message content consist of objects of well defined classes rather than of structured text.

### IceGrid

is a suite of frameworks that provide object-oriented load balancing, failover, object-discovery and registry services.

### IcePatch

facilitates the deployment of ICE-based software. For example, a user who wishes to deploy new functionality and/or patches to several servers may use IcePatch.

### Glacier

is a proxy-based service to enable communication through firewalls, thus making ICE an internet communication engine.

### IceBox

Icebox is a service-oriented architecture container of executable services implemented in .dll or .so libraries. This is a lighter alternative to building entire executable for every service.

### Slice

Slice is a ZeroC-proprietary file format that programmers follow to edit computer-language independent declarations and definitions of classes, interfaces, structures and enumerations. Slice definition files are used as input to the stub generating process. The stub in turn is linked to applications and servers that should communicate with one another based on interfaces and classes as declared/defined by the slice definitions.

Apart from CORBA, classes and interfaces support inheritance and abstract classes. In addition, slice provides configuration options in form of macros and attributes to direct the code generation process. An example is the directive to generate a certain STL `list<double>` template instead of the default, which is to generate a STL `vector<double>` template.

## See also

* Cisco's Etch
* Google's gRPC
* SOAP
* Apache Thrift
* Microsoft's WCF

## Notes

1. ↑ "Ice - Comprehensive RPC Framework". http://zeroc.com/products/ice#everywhere.
2. ↑ "Ice - Comprehensive RPC Framework". https://zeroc.com/products/ice#flexible.
3. ↑ "Does ICE uses any http protocol for communication" (in en). https://forums.zeroc.com/discussion/46698/does-ice-uses-any-http-protocol-for-communication.
4. ↑ Laukien, Marc. "Project: The Internet Communications Engine". https://forums.zeroc.com/discussion/22/the-internet-communications-engine.
5. ↑ "Differences between Ice and CORBA". http://www.zeroc.com/iceVsCorba.html.
6. ↑ Michi Henning (February 1, 2004). "Massively Multiplayer Middleware". Queue (ACM). http://queue.acm.org/detail.cfm?id=971591. Retrieved July 17, 2013.
7. ↑ Sergij Shumko (November 2, 2008). "Ice middleware in the New Solar Telescope's Telescope Control System". Quebec City, Canada. http://solar.njit.edu/preprints/shumko1395.pdf. Retrieved July 17, 2013.
8. ↑ Normier, Bernard. "Ice has moved to GitHub!". https://forums.zeroc.com/discussion/6600/ice-has-moved-to-github.

## External links

* https://github.com/zeroc-ice/ice

0.00

(0 votes)

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Software:Internet_Communications_Engine&oldid=745720"