Internet Communications Engine

From Wikipedia, the free encyclopedia
Jump to: navigation, search
Internet Communications Engine
Developer(s) ZeroC
Stable release 3.4.2 / September 7, 2011; 2 years ago (2011-09-07)
Preview release 3.5b / May 15, 2011; 3 years ago (2011-05-15)
Type Remote procedure call framework
License GPL / Proprietary
Website www.zeroc.com

The Internet Communications Engine, or Ice, is an object-oriented middleware platform that provides object-oriented remote procedure call, grid computing and publish/subscribe functionality developed by ZeroC and dual-licensed under the GNU General Public License and a proprietary license. It supports C++, Java, .NET-languages (such as C# or Visual Basic), Objective-C, Python, PHP and Ruby[1] on most major operating systems such as Linux, Solaris, Windows and Mac OS X. A light variant of Ice runtime, called Ice-e,[2] may run inside mobile phones. As its name indicates, the middleware may be used for applications without the need to use the HTTP protocol and is capable of traversing firewalls unlike other middleware of that time.

History[edit]

ZeroC was founded in 2002 in Florida.[3] 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.[4]

In 2004, it was reported that a game called "Wish" by a company named Mutable Realms used Ice.[5] In 2008, it was reported that Big Bear Solar Observatory had used the software since 2005.[6] Some versions were posted to GitHub as part of the Open Microscopy Environment, through the 3.4.2 version in 2011.[7]

Components[edit]

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.

ICEgrid.png

IceStorm[edit]

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[edit]

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

IcePatch[edit]

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[edit]

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

IceBox[edit]

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[edit]

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[edit]

Notes[edit]

  1. ^ http://zeroc.com/languages.html. Retrieved on 2009-08-03.
  2. ^ http://zeroc.com/icee/index.html. Retrieved on 2009-08-03.
  3. ^ "Zeroc, Inc". Corporate profile. Manta. Retrieved July 17, 2013. 
  4. ^ "Differences between Ice and CORBA". Archived from the original on March 18, 2013. Retrieved July 17, 2013. 
  5. ^ Michi Henning (February 1, 2004). "Massively Multiplayer Middleware". Queue (ACM). Retrieved July 17, 2013. 
  6. ^ Sergij Shumko (November 2, 2008). "Ice middleware in the New Solar Telescope's Telescope Control System". Astronomical Data Analysis Software and Systems XVII, ASP Conference Series, Vol. XXX, 2008. Quebec City, Canada. Retrieved July 17, 2013. 
  7. ^ "ome/zeroc-ice". Source code download. GitHub. Retrieved July 17, 2013. 

External links[edit]