Since the 1990s, the computing industry has been using DCOM [3] and
CORBA [4] This object-oriented middleware platform. Make distributed computing to application developers
In the process used, object-oriented middleware is a very important step. Developers have the first time
This may: do not have to be a network Guru, you can build a distributed application -
The middleware platform will take advantage of most of the network hybrids, such as Marshaling and Underson
(Unmarshaling) (encoding the data and decoding for transmission), put the logical object address
Map to the physical transmission endpoint, change the data of the data according to the original machine architecture of the customer and server
Show, and automatic start of the server.
However, due to some reasons, both DCOM or CORBA failed to succeed
Partial computing market:
• DCOM is a exclusive solution for Microsoft, in which a variety of machines will run more
Operating system, you cannot use DCOM.
• DCOM cannot support a large number of objects (hundreds of thousands or millions), which is largely it is its
The overhead of distributed garbage collection mechanism is caused.
• Although there are several suppliers to provide CORBA products, it is almost impossible to find a supplier.
Enough to provide all the environments in the xenocarbon network. Despite the large number of standardization work, no
There is still lack of interoperability between the same CORBA implementation, thereby constantly causing various problems;
Moreover, since suppliers often define their own expansion, CORBA lacks for multi-threaded rings
The specification of the world, for language like C or C , source compatibility has never been fully implemented.
• DCOM and CORBA are too complicated. Be familiar with DCOM or CORBA, and carry out
Design and programming is a difficult task that needs to be mastered in many months (but to reach an expert.
Level, take for several years)
• Performance issues have been torture these two platforms in their respective history. DCOM has only one
Implementation is available, so it is impossible to purchase better performance. Although there are several suppliers offered
Corba products, it is difficult to find compliance standards, good performance - the main reason is
The complexity of the CORBA specification (in many cases, its characteristics are exceeding
Needed in need)
• In the heterogeneous environment, let DCOM and CORBA have never been an easy task:
Although there are suppliers to provide interoperability products, interoperability between these two platforms has never been
Sewing, and difficult to manage, will produce silos that are not connected to each other.
In 2002, Microsoft .NET platform [11] replaced DCOM. But although .net is available.
More powerful distributed computing than DCOM, it is still a exclusive solution for Microsoft,
Therefore, it is not a choice of choices. On the other hand, CORBA has stagnated, many in recent years.
The supplier left the market and left the consumer and no longer received a widely supported platform;
The number of suppliers has declined in further standardization, resulting in a permanent in CORBA specifications.
Multi-defects have not been resolved or resolved after many years of reporting.
While DCOM and CORBA decline, distributed computing community pairs of SOAP [23] and Web
Services [24] has a strong interest. Use an ubiquitous WWW infrastructure and HTTP
The idea of developing the middleware platform is very fascinating - at least in theory. SOAP and Web
Services has promised to be a distributed computing universal language on the Internet. But although a large public effect has been introduced, many papers have been published, but Web Services can not be fulfilled:
While writing this book, there are very few commercial systems developed by Web Services architecture. The reason is:
• Whether in terms of network bandwidth, SOAP will cause applications
Severe performance is deteriorating, so that this technology cannot be applied to many systems with harsh performance requirements.
System.
• Although SOAP provides the "ON-THE-WIRE" specification, it is still not enough to develop real-world applications.
Because the abstract level provided by this specification is too low. Application can put all kinds of SOAP messages
Together, this is extremely cumbersome and error-free.
• The lack of more advanced abstraction enables suppliers to provide a variety of application development platforms to comply with SOAP
Application development automation. However, in addition to the primary level, these development platforms are completely free of standard
Chemical, inevitably private, so the application developed by a supplier cannot be supplied with other supplies
User's middleware products are used together.
• About SOAP and Web Services architectural security, there are some serious concerns [15]. especially
Land, many experts say they are worried about the lack of intrinsic security of the platform.
• DCOM and CORBA are too complicated. Be familiar with DCOM or CORBA, and carry out
Design and programming is a difficult task that needs to be mastered in many months (but to reach an expert.
Level, take for several years)
• Performance issues have been torture these two platforms in their respective history. DCOM has only one
Implementation is available, so it is impossible to purchase better performance. Although there are several suppliers offered
Corba products, it is difficult to find compliance standards, good performance - the main reason is
The complexity of the CORBA specification (in many cases, its characteristics are exceeding
Needed in need)
• In the heterogeneous environment, let DCOM and CORBA have never been an easy task:
Although there are suppliers to provide interoperability products, interoperability between these two platforms has never been
Sewing, and difficult to manage, will produce silos that are not connected to each other.
In 2002, Microsoft .NET platform [11] replaced DCOM. But although .net is available.
More powerful distributed computing than DCOM, it is still a exclusive solution for Microsoft,
Therefore, it is not a choice of choices. On the other hand, CORBA has stagnated, many in recent years.
The supplier left the market and left the consumer and no longer received a widely supported platform;
The number of suppliers has declined in further standardization, resulting in a permanent in CORBA specifications.
Multi-defects have not been resolved or resolved after many years of reporting.
While DCOM and CORBA decline, distributed computing community pairs of SOAP [23] and Web
Services [24] has a strong interest. Use an ubiquitous WWW infrastructure and HTTP
The idea of developing the middleware platform is very fascinating - at least in theory. SOAP and Web
Services has promised to be a distributed computing universal language on the Internet. But despite triggering
A large public effect, published many papers, Web Services did not fulfill their promise:
While writing this book, there are very few commercial systems developed by Web Services architecture. The reason is:
• Whether in terms of network bandwidth, SOAP will cause applications
Severe performance deteriorates so that this technology is unable to apply to systems with harsh performance requirements.
• Although SOAP provides the "ON-THE-WIRE" specification, it is still not enough to develop real-world applications.
Because the abstract level provided by this specification is too low. Application can put all kinds of SOAP messages
Together, this is extremely cumbersome and error-free.
• The lack of more advanced abstraction enables suppliers to provide a variety of application development platforms to comply with SOAP
Application development automation. However, in addition to the primary level, these development platforms are completely free of standard
Chemical, inevitably private, so the application developed by a supplier cannot be supplied with other supplies
User's middleware products are used together.
• About SOAP and Web Services architectural security, there are some serious concerns [15]. especially
Land, many experts say they are worried about the lack of intrinsic security of the platform.
Internet Communications Engine (ICE)
For these unhappy options, Zeroc, Inc. decided to develop Internet Communications
ENGINE, referred to as ICE1. Its main design goals are:
• Provide object-oriented middleware platforms for use in xenografts.
• Provide a set of complete features that support the development of practical distributed applications in a wide range of fields.
• Avoid unnecessary complexity to make the platform easier to learn and use.
• Provide a very efficient implementation of network bandwidth, memory usage, and CPU overhead.
• Provides an implementation with built-in security to make it suitable for unsafe public networks.
Simplely said that ICE design goals can be stated: "Let us build as strong as CORBA
The big middleware platform does not make any mistakes committed by CORBA.
