RPC Communication Framework--RCF Introduction (replace COM)

Read Catalogue

• RPC Communication Framework
• Why Choose RCF
• Simple performance Test
• Resources
• Summarize

The existing software uses a large number of COM interfaces, resulting in the inability to cross the platform, of course, due to the combination of Windows too close, there are many can not cross the platform of the place. So in order to achieve cross-platform, support Linux system, and subsequent distributed, the first task is to remove the COM interface.

After investigating a large number of frameworks, it was decided to replace the COM interface with RCF.

Back to top RPC communication framework

1. Corba
2. ICE
3. Thrift
4. Zeromq
5. Dbus
6. Rcf
7. YAMI4
8. TAO

Back to the top why choose RCF

After various comparisons, we think:

1. RCF is used in much the same way as existing COM interfaces, where it can be faster and easier to replace COM and less prone to errors;
2. In terms of stability, RCF from the first official version of 2008 released 1.0, to the present 2.01, experienced 7 major version changes, the development of users, including "Ericsson, Hewlett-Packard" and other such large companies, on the network to find RCF-related introductions, generally speaking good, is a more powerful distributed communication framework, so RCF is relatively stable, relatively mature;
3. RCF based on standard C + +, support windows, Linux, UNIX and other operating systems, can be very good to complete cross-platform functions;
4. RCF supports TCP, UDP, named Pipes and other communication methods;
5. RCF server supports single threaded and thread pooling patterns, which correspond to the two threading patterns of COM;
6. The official document claims to use 0 copies, 0 heap memory allocations, server-side caching and other technologies to improve performance;
7. More importantly, although the official only English documents, but this document is very easy to understand, even if the English level is poor, but also in a night or a morning time on the use of RCF overall, including features, supported protocols, etc. have a more detailed understanding of the subsequent rapid understanding and rapid development and replacement of COM , has a vital role to play;

Go back to the top for a simple performance test

In my Notebook Windows7 Professional Edition SP1 x64, Intel (R) Core (TM) i5-2450m CPU @ 2.5GHz, 12G memory on the machine, the demo was written to test RCF.

A server program, a client program, communication through TCP, the client program calls the Server service interface, this interface implementation is an empty method to test the limit number of pure interface calls, release version x86 test results are as follows:

Calls 20,000 times, takes about 1647ms, the average can be called 12,143 times per second, averaging 82 subtle calls per call.

Back to top references

Recommended: Process scheduling library, inter-process communication library, all open source, thank you! -c/c++-chinaunix.net

Rcf-interprocess Communication for C++–codeproject

Several ways of distributed communication (EJB, RMI, RPC, JMS, Web service talk)

A/C + + Distributed application/Grid open source software

What are the main open source distributed system architectures now?

Thrift Introductory Introduction

Apache Thrift-Scalable cross-language service development Framework

Cross platform IPC

Back to top of the summary

After each comparison, although RCF is not the most powerful framework and may not be the most performance framework, but in the case of replacing the requirements of the COM interface, RCF should be the most appropriate framework, so the RCF framework is ultimately chosen to accomplish this task.

Http://www.cnblogs.com/hbccdf/p/RCF_introduce.html

RPC Communication Framework--RCF Introduction (replace COM)