Internet Communications Engine
3.7.2 / February 5, 2019
|Type||Remote procedure call framework|
|License||GPL / Proprietary|
Ice implements a proprietary application layer communications protocol, called the Ice protocol, that can run over TCP, TLS, UDP, WebSocket and Bluetooth. As its name indicates, Ice can be suitable for applications that communicate over the Internet, and includes functionality for traversing firewalls.
ZeroC was founded in 2002 in Florida. 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.
In 2004, it was reported that a game called "Wish" by a company named Mutable Realms used Ice. In 2008, it was reported that Big Bear Solar Observatory had used the software since 2005. The source code repository for Ice is on GitHub since May 2015.
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.
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.
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.
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
- http://zeroc.com/products/ice#everywhere Retrieved on 2018-04-27.
- https://zeroc.com/products/ice#flexible Retrieved on 2019-02-08
- "Does ICE uses any http protocol for communication". ZeroC. Retrieved 2019-08-13.
- "Zeroc, Inc". Corporate profile. Manta. Retrieved July 17, 2013.
- "Differences between Ice and CORBA". Archived from the original on March 18, 2013. Retrieved July 17, 2013.
- Michi Henning (February 1, 2004). "Massively Multiplayer Middleware". Queue. ACM. Retrieved July 17, 2013.
- Sergij Shumko (November 2, 2008). "Ice middleware in the New Solar Telescope's Telescope Control System" (PDF). Astronomical Data Analysis Software and Systems XVII, ASP Conference Series, Vol. XXX, 2008. Quebec City, Canada. Archived from the original (PDF) on August 25, 2012. Retrieved July 17, 2013.
- Normier, Bernard. "Ice has moved to GitHub!". ZeroC Forums. Retrieved 8 February 2019.