Remote Call Framework 3.1

Transport Access

Server and client transports are responsible for the actual transmission and reception of network messages. A RcfServer contains one or more server transports, while a client contains only a single client transport.

To access the server transports of a RcfServer, capture the return value of RcfServer::addEndpoint():

RCF::ServerTransport & serverTransportTcp = server.addEndpoint(
RCF::TcpEndpoint(50001) );
RCF::ServerTransport & serverTransportUdp = server.addEndpoint(
RCF::UdpEndpoint(50002) );

Alternatively, if the RcfServer only has a single server transport, you can access it by calling RCF::RcfServer::getServerTransport():

RCF::RcfServer server( RCF::TcpEndpoint(50001) );
RCF::ServerTransport & serverTransport = server.getServerTransport();

On the client side, the client transport is availablable through RCF::ClientStub::getTransport():

RcfClient<I_Echo> client( RCF::TcpEndpoint(50001) );
RCF::ClientTransport & clientTransport = client.getClientStub().getTransport();

Transport Configuration

Maximum Incoming Message Lengths

For server-side transports, it is generally necessary to set an upper limit on the size of incoming network messages. Without an upper limit, it is possible for malformed requests to cause arbitrarily sized memory allocations on the server.

The maximum incoming message length setting of a RCF server transport defaults to 1 Mb, and can be changed by calling RCF::ServerTransport::setMaxIncomingMessageLength() :

// Set max message length to 5 Mb.

Similarly, there is a maximum incoming message length setting for client transports. It defaults to 1 Mb and can be changed by calling RCF::ClientTransport::setMaxIncomingMessageLength() :

RcfClient<I_Echo> client( RCF::TcpEndpoint(123) );
// Set max message length to 5 Mb.

As client transports only receive network messages from a peer they have connected to, the risk of malformed packets is not as great as for server transports.

It is possible to query a RcfClient<> for the sizes of the latest request and response messages sent:

RcfClient<I_Echo> client( RCF::TcpEndpoint(50001) );
// Retrieve request and response size of the previous call.
RCF::ClientTransport & transport = client.getClientStub().getTransport();
std::size_t requestSize = transport.getLastRequestSize();
std::size_t responseSize = transport.getLastResponseSize();

Connection Limits

To set the maximum number of simultaneous connections to a RCF server transport:

// Allow at most 100 clients to be connected at any time.

This setting is not relevant to the UDP server transport, as there is no concept of connections within the UDP protocol.

System Port Selection

For IP-based server transports, you can allow the local system to assign a server port number automatically, by specifying 0 as the port number. When the server starts, the system will find a free port and assign it to the server. The port number can subseqently be retrieved through RCF::IpServerTransport::getPort():

int port = server.getIpServerTransport().getPort();
RcfClient<I_Echo> client(( RCF::TcpEndpoint(port) ));

IP-based Access Rules

For IP-based server transports, client access can be allowed or denied, based on the IP addresses of the clients.

To configure IP rules for allowing clients, use RCF::IpServerTransport::setAllowIps():

RCF::IpServerTransport & ipTransport =
dynamic_cast<RCF::IpServerTransport &>(server.getServerTransport());
std::vector<RCF::IpRule> rules;
// Match 11.22.33.* (24 significant bits).
rules.push_back( RCF::IpRule( RCF::IpAddress(""), 24) );
// Access will be granted to clients connecting from IP addresses matching 11.22.33.* .
// All other clients will be denied.

To configure IP rules for denying clients, use RCF::IpServerTransport::setDenyIps():

RCF::IpServerTransport & ipTransport =
dynamic_cast<RCF::IpServerTransport &>(server.getServerTransport());
std::vector<RCF::IpRule> rules;
// Match 11.*.*.* (8 significant bits).
rules.push_back( RCF::IpRule( RCF::IpAddress(""), 8) );
// Match 12.22.*.* (16 significant bits).
rules.push_back( RCF::IpRule( RCF::IpAddress(""), 16) );
// Access will be denied to clients connecting from IP addresses matching 11.*.*.* and 12.22.*.* .
// All other clients will be allowed.


RCF supports both IPv4 and IPv6. IPv6 support is enabled by default in RCF, but you can define RCF_FEATURE_IPV6=0 to disable it (see Building RCF).

For example, to run a server and client over a loopback IPv4 connection:

// Specifying an explicit IPv4 address to bind to.
RCF::RcfServer server( RCF::TcpEndpoint("", 50001) );
// Specifying an explicit IPv4 address to bind to.
RcfClient<I_Echo> client( RCF::TcpEndpoint("", 50001) );

To run a server and client over a loopback IPv6 connection instead, specify ::1 instead of

// Specifying an explicit IPv6 address to bind to.
RCF::RcfServer server( RCF::TcpEndpoint("::1", 50001) );
// Specifying an explicit IPv6 address to bind to.
RcfClient<I_Echo> client( RCF::TcpEndpoint("::1", 50001) );

RCF uses the POSIX getaddrinfo() function to resolve IP addresses. getaddrinfo() can return either IPv4 or IPv6 addresses, depending on the configuration of the local system and network. So the following client will use either IPv4 or IPv6, depending on how the local system and network have been configured:

// Will resolve to either IPv4 or IPv6, depending on what the system
// resolves machine.domain to.
RcfClient<I_Echo> client( RCF::TcpEndpoint("machine.domain", 50001) );

You can force IPv4 or IPv6 resolution by using the RCF::IpAddressV4 and RCF::IpAddressV6 classes:

// Force IPv4 address resolution.
RCF::IpAddressV4 addr_4("machine.domain", 50001);
RcfClient<I_Echo> client_4(( RCF::TcpEndpoint(addr_4) ));
// Force IPv6 address resolution.
RCF::IpAddressV6 addr_6("machine.domain", 50001);
RcfClient<I_Echo> client_6(( RCF::TcpEndpoint(addr_6) ));

On machines with dual IPv4/IPv6 stacks, you will probably want your server to listen on both IPv4 and IPv6 addresses. To do this portably, you should listen on both and ::0:

// Listen on port 50001, on both IPv4 and IPv6.
server.addEndpoint( RCF::TcpEndpoint("", 50001) );
server.addEndpoint( RCF::TcpEndpoint("::0", 50001) );

On some platforms, it is sufficient to listen only on ::0, as the system will translate incoming IPv4 connections into IPv6 connections with a special class of IPv6 addresses.

Local Address Bindings for Clients

When a RcfClient<> connects to a server using an IP-based transport, the default behavior is to allow the system to decide which local network interface and local port to use. In some circumstances, you may want to explicitly set the local network interface a client should bind to.

You can do so by calling RCF::IpClientTransport::setLocalIp(), before connecting:

RcfClient<I_Echo> client( RCF::TcpEndpoint("", 50001) );
RCF::IpClientTransport & ipTransport =
// Force client to bind to a particular local network interface (
ipTransport.setLocalIp( RCF::IpAddress("", 0) );

After a RcfClient<> has connected, you can determine which local network interface and port it is bound to, by calling RCF::IpClientTransport::getAssignedLocalIp():

RcfClient<I_Echo> client( RCF::TcpEndpoint("", 50001) );
RCF::IpClientTransport & ipTransport =
// Find out which local network interface the client is bound to.
RCF::IpAddress localIp = ipTransport.getAssignedLocalIp();
std::string localInterface = localIp.getIp();
int localPort = localIp.getPort();

Socket Level Access

RCF provides access to the underlying OS primitives, such as sockets and handles, of client and server transports. For example:

// Client-side.
RcfClient<I_Echo> client( RCF::TcpEndpoint("", 50001) );
RCF::TcpClientTransport & tcpClientTransport =
dynamic_cast<RCF::TcpClientTransport &>(
client.getClientStub().getTransport() );
// Obtain client socket handle.
int sock = tcpClientTransport.getNativeHandle();
// Server-side.
RCF::NetworkSession & networkSession = RCF::getCurrentRcfSession().getNetworkSession();
RCF::TcpNetworkSession & tcpNetworkSession =
dynamic_cast<RCF::TcpNetworkSession &>(networkSession);
// Obtain server socket handle.
int sock = tcpNetworkSession.getNativeHandle();

This can be useful if you need to set custom socket options.

Transport Implementations

This sections covers the various transport types that are implemented in RCF.


TCP endpoints are represented in RCF by the RCF::TcpEndpoint class, constructed from an IP address and a port number.

RCF::RcfServer server( RCF::TcpEndpoint("", 50001) );
RcfClient<I_Echo> client( RCF::TcpEndpoint("", 50001) );

Server transports interpret the IP address as the local network interface to listen on. So for example "" should be specified in order to listen on all available IPv4 network interfaces, and "" should be specified to listen only on the loopback IPv4 interface. If no IP address is specified, "" is assumed.


Like RCF::TcpEndpoint, RCF::UdpEndpoint is constructed from an IP address and a port.

RCF::RcfServer server( RCF::UdpEndpoint("", 50001) );
RcfClient<I_Echo> client( RCF::UdpEndpoint("", 50001) );

RCF::UdpEndpoint also contains some extra functionality, to deal with multicasting and broadcasting.


RCF::UdpEndpoint can be configured to listen on a multicast IP address:

// Listen on multicast address, on port 50001, on all network interfaces.
RCF::UdpEndpoint udpEndpoint("", 50001);
RCF::RcfServer server(udpEndpoint);

Note that the server still needs to specify a local network interface to listen on.

To send multicast messages, specify a multicast IP address and port when creating the client:

RcfClient<I_Echo> client( RCF::UdpEndpoint("", 50001) );
client.Echo(RCF::Oneway, "ping");


To send broadcast messages, specify a broadcast IP address and port:

RcfClient<I_Echo> client( RCF::UdpEndpoint("", 50001) );
client.Echo(RCF::Oneway, "ping");

Address Sharing

RCF's UDP server transport can be configured to share its address binding, so that multiple RcfServer's can listen on the same port of the same interface. This is enabled by default when listening on multicast addresses, but can also be enabled when listening on non-multicast addresses. This can be useful if multiple processes on the same machine need to listen to the same broadcasts:

EchoImpl echoImpl;
RCF::UdpEndpoint udpEndpoint1("", 50001);
RCF::RcfServer server1(udpEndpoint1);
RCF::UdpEndpoint udpEndpoint2("", 50001);
RCF::RcfServer server2(udpEndpoint2);
// This broadcast message will be received by both servers.
RcfClient<I_Echo> client( RCF::UdpEndpoint("", 50001) );
client.Echo(RCF::Oneway, "ping");

Server Discovery

In situations where servers are started on dynamically assigned ports, multicasting and broadcasting can be a useful means of communicating server IP addresses and ports to clients. For example:

// Interface for broadcasting port number of a TCP server.
RCF_BEGIN(I_Broadcast, "I_Broadcast")
RCF_METHOD_V1(void, ServerIsRunningOnPort, int)
// Implementation class for receiving I_Broadcast messages.
class BroadcastImpl
BroadcastImpl() : mPort()
void ServerIsRunningOnPort(int port)
mPort = port;
int mPort;
// A server thread runs this function, to broadcast the server location once
// per second.
void broadcastThread(int port, const std::string &multicastIp, int multicastPort)
RcfClient<I_Broadcast> client(
RCF::UdpEndpoint(multicastIp, multicastPort) );
// Broadcast 1 message per second.
while (true)
// ***** Server side ****
// Start a server on a dynamically assigned port.
EchoImpl echoImpl;
// Retrieve the port number.
int port = server.getIpServerTransport().getPort();
// Start broadcasting the port number.
RCF::ThreadPtr broadcastThreadPtr(new RCF::Thread(
[=]() { broadcastThread(port, "", 50001); }));
// ***** Client side ****
// Clients will listen for the broadcasts before doing anything else.
RCF::UdpEndpoint udpEndpoint("", 50001);
RCF::RcfServer clientSideBroadcastListener(udpEndpoint);
BroadcastImpl broadcastImpl;
// Wait for a broadcast message.
while (!broadcastImpl.mPort)
// Once the clients know the port number, they can connect.
RcfClient<I_Echo> client( RCF::TcpEndpoint(broadcastImpl.mPort));

Note that here we are actually using a multicast address to broadcast information to clients. If multicasting had been unavailable on this particular network, we could also have used an IP broadcast address instead of an IP multicast address.

Win32 Named Pipes

RCF supports Win32 named pipe transports. RCF::Win32NamedPipeEndpoint takes one constructor parameter, which is the name of the named pipe, with or without the leading \\.\pipe\ prefix.

RCF::RcfServer server( RCF::Win32NamedPipeEndpoint("PrintSvrPipe") );
RcfClient<I_Echo> client( RCF::Win32NamedPipeEndpoint("PrintSvrPipe") );

An advantage of using Win32 named pipes, is that they allow easy authentication of clients. A server using a Win32 named pipe server transport can authenticate its clients through the RCF::Win32NamedPipeImpersonator class, which uses the Windows API function ImpersonateNamedPipeClient() to impersonate the client:

RCF_BEGIN(I_Echo, "I_Echo")
RCF_METHOD_R1(std::string, Echo, const std::string &)
class EchoImpl
std::string Echo(const std::string & s)
// Impersonate client.
RCF::Win32NamedPipeImpersonator impersonator(RCF::getCurrentRcfSession());
std::cout << "Client user name: " << RCF::getMyUserName();
return s;

If we had used a TCP connection to instead, we would have needed to enable Kerberos or NTLM authentication to securely determine the clients user name (see Transport protocols).

UNIX Domain Sockets

UNIX domain sockets function analogously to Win32 named pipes, and allow efficient communication between servers and clients on the same machine. RCF::UnixLocalEndpoint takes one parameter, which is the name of the UNIX domain socket. The name must be a valid filesystem path. For servers, the program must have sufficient privilege to create the given path, and the file must not already exist. For clients, the program must have sufficient privilege to access the given path.

Here is a simple example:

RCF::RcfServer server( RCF::UnixLocalEndpoint("/home/xyz/MySocket"));
RcfClient<I_Echo> client( RCF::UnixLocalEndpoint("/home/xyz/MySocket"));


RCF supports tunneling remote calls over the HTTP and HTTPS protocols. In particular, remote calls can be directed through HTTP and HTTPS proxies.

HTTPS is essentially the HTTP protocol layered on top of the SSL protocol. As such, configuration of the SSL aspects of HTTPS, is done in the same way as for the SSL transport protocol (see Transport protocols).


To setup a server with an HTTP endpoint, use RCF::HttpEndpoint:

RCF::RcfServer server( RCF::HttpEndpoint("", 80) );
PrintService printService;

Similarly, for an HTTPS endpoint, use RCF::HttpsEndpoint:

RCF::RcfServer server( RCF::HttpsEndpoint("", 443) );
PrintService printService;
"CertificateName") ) );


Client side configuration is similar, using RCF::HttpEndpoint for a HTTP client:

RcfClient<I_PrintService> client( RCF::HttpEndpoint("", 80) );
client.Print("Hello World");

, and RCF::HttpsEndpoint for a HTTPS client:

RcfClient<I_PrintService> client( RCF::HttpsEndpoint("", 443) );
client.Print("Hello World");

Finally, to direct remote calls through a HTTP or HTTPS proxy, use the RCF::ClientStub::setHttpProxy() and RCF::ClientStub::setHttpProxyPort() functions:

client.Print("Hello World");

Reverse proxies

HTTP reverse proxies are common on the Internet, and are used to provide functionality such as load balancing and SSL offloading for back-end HTTP servers.

Reverse proxies are generally transparent to the client and destination servers. You can place a reverse proxy between a RCF client and a server, and this provides an out-of-the-box mechanism for distributing load across a set of RCF servers.

In load-balancing scenarios, you may want a RCF client to continue sending requests to the same back-end server that it initially connects to. To accomplish this, you will need to use a reverse proxy with support for session affinity. Session affinity is normally implemented by the reverse proxy, by inserting a special HTTP cookie in the initial HTTP response of the communication stream. The RCF client will then automatically include this cookie on subsequent requests, allowing the reverse proxy to route subsequent requests through to the same back-end server.

If you have multiple RCF client connections, you can configure them to connect to the same back-end server, by retrieving the HTTP cookies from the first connection and subsequently applying them to the other connections (see RCF::ClientStub::setHttpCookies()).

Another reverse proxying feature you can utilize with RCF is SSL offloading. With SSL offloading , the RCF client connects using a HTTPS connection, but the HTTPS connection is decrypted by the reverse proxy, and the decrypted HTTP stream is forwarded on to the back-end server. This allows secure communication between the client and the back-end server, with the reverse proxy assuming the load of SSL encryption/decryption. This also has the advantage of centralizing certificate configuration, from multiple back-end servers, to the reverse proxy server.

RCF has been tested with the following reverse proxies: