2

Is there any benchmark about encoding/decoding certain common typed data in Microsoft RPC NDR engine (DCE 1.1) in comparison with that in XML-RPC-C/C++ in the de-facto C/C++ implementation in XML-RPC?

Actually I have to choose between Windows RPC and XML-RPC-C/C++ to implement my own common object infrastructure for High Performance Computing on Windows. Any recommandation about which with regard to their performance? Thank you.

Best Regards,

Yang

Y.Z
  • 626
  • 2
  • 9
  • 21
  • DCE uses a binary protocol while XML-RPC uses XML on top of HTTP. I would expect that DCE is faster. Also it is deeply integrated into Windows and there are various tools in the SDK to support it (`midl` for example). I've used XML-RPC to connect a Python GUI to a C++ backend on Linux but the C++ XML-RPC implementation was tedious to use. Why not just use DCOM (which runs on top of DCE)? (Pardon my curiosity but what exactly HPC task are you going to achieve using distributed objects?) – Hristo Iliev Jun 06 '12 at 12:45
  • @HristoIliev Hmm...DCOM should be what I'm looking for. It's not exactly about HPC task but currently an infrastructure of common object storage based on DHT that allows further implementation of channel in Hoare's CSP. I use DHT for scalable and fault-tolerant naming as well as load balancing of those objects. Microsoft has been doing the same in WCF, namely Peer Name Resolution Protocol (PRNP) in the recent .NET framework 3.5. – Y.Z Jun 07 '12 at 10:31
  • Correction: DCOM is not applicable here. – Y.Z Jun 07 '12 at 10:46

0 Answers0