Comments on: RCF: C++ apps speaking their mother tongue http://blog.davber.com/2006/08/19/rcf-c-apps-speak-their-mother-tongue/ Functional functional programming - Haskell, Ruby, Erlang, Scala... Mon, 04 Jan 2010 21:38:57 -0500 http://wordpress.org/?v=2.8.4 hourly 1 By: fox_three http://blog.davber.com/2006/08/19/rcf-c-apps-speak-their-mother-tongue/comment-page-1/#comment-7 fox_three Thu, 31 Aug 2006 18:06:41 +0000 http://blog.davber.com/?p=16#comment-7 The only nit I'll pick is that RCF::Twoway means that the client makes a standard request-response call, while RCF::Oneway means that only a request is made, and no response is sent back from the server. On an unreliable transport like UDP, you don't want to wait around for a response, because it might get lost on the network, so in that case RCF::Oneway is more natural (fire and forget). RCF::Twoway is for reliable transports like TCP, although UDP on localhost is probably pretty reliable too :) Thanks for the review! Jarl. The only nit I’ll pick is that RCF::Twoway means that the client makes a standard request-response call, while RCF::Oneway means that only a request is made, and no response is sent back from the server.

On an unreliable transport like UDP, you don’t want to wait around for a response, because it might get lost on the network, so in that case RCF::Oneway is more natural (fire and forget). RCF::Twoway is for reliable transports like TCP, although UDP on localhost is probably pretty reliable too :)

Thanks for the review!

Jarl.

]]>