RPC communication framework-RCF introduction, rpc framework rcf
The existing software uses a large number of COM interfaces, resulting in the inability to cross-platform. Of course, due to the tight combination with Windows, there are still many areas where cross-platform access is unavailable. In order to implement cross-platform support for Linux and subsequent distribution, the first task is to remove the COM interface.
After investigating a large number of frameworks, I decided to use RCF to replace the COM interface.
Why does RPC communication framework choose RCF?
After comparison, I think:
Simple Performance Testing
In my notebook Windows 7 Pro SP1 x64, Intel (R) Core (TM) i5-2450M CPU @ 2.5 GHz, 12g memory machine, compiled a Demo, RCF was tested.
A Server program and a Client program communicate over TCP. The Client program calls the Server service interface. This interface is implemented as an empty method to test the limit times of pure interface calls, release x86 test results:
20 thousand calls, about 12143 ms, calls per second on average, 82 subtle times per call.
References
Recommendation: Process Scheduling library, inter-process communication library, All open source, thank you! -C/C ++ -ChinaUnix.net
RCF-Interprocess Communication for C ++-CodeProject
Distributed communication methods (EJB, RMI, RPC, JMS, and web service)
C/C ++ distributed application/GRID open source software
What are the mainstream Open-Source Distributed System architectures?
Thrift Introduction
Apache Thrift-scalable cross-language service development framework
Cross platform IPC
Summary
After comparison, although RCF is not the most powerful framework, it may not be the most performance framework, but with the need to replace the COM interface, RCF should be the most suitable framework, so the RCF framework is chosen to complete this task.