Delta V Software Forums

You'll need to apply a session timeout to your server. Here's how to do it in RCF 2.0: RCF::RcfServer server; // Sessions idle for 5 minutes will be terminated. server.setSessionTimeoutMs(5*60*1000); // Scan for idle sessions every 60 seconds. server.setSessionHarvestingIntervalMs(1*60*1000); server...

The simplest way to do this is to run a RcfServer in both the client and server. If you use named pipes with names known to both the server and the client, they won't have any problems finding each other. If you use TCP, you'll need to use fixed port numbers, or else have some other way of communica...

You need to use RcfServer::setOnCallbackConnectionCreated() , to get notified of whenever a callback connection is created. The sample code in the User Guide does this: RCF::RcfServer server( RCF::TcpEndpoint(0) ); server.setOnCallbackConnectionCreated(onCallbackConnectionCreated); server.start(); F...

I've had a go at stripping the codebase down to a minimum, and ended up with an executable containing a TCP server and client, with a size of 500kb. That's to be compared to a size of 1Mb, before I started stripping code out. With a bit more work I'm pretty sure it can go a ways under 500kb as well....

Thanks for reporting this. There is a new build in the works, and I've put a fix in for it.

If I understand correctly, you want to be able to make calls from the server to the client, and from the client to the server. The easiest way to do that is for the client to create two RcfClient<> objects, and call createCallbackConnection() on one of them. That way both the server and the client w...

I would expect lower file size than that, but it is difficult to make any predictions. For comparison, when building RCF as a DLL with Visual Studio 2012, in 32 bit release, the resulting DLL is 1289 kb. The same DLL, when built in 64 bit release, is 1910 kb. If I instead build a simple application ...

Thanks for the detailed description. What's happening is that when RCF::createCallbackConnection() is called, the network connection is removed from the RcfClient<> object, and taken over by the RcfServer. When you make a subsequent call on the same RcfClient<> object, a new network connection is cr...

No problem Volker. I haven't used boost::chrono myself, so I don't know how steady_clock etc works. However, to serialize something that represents a point in time, you could format it as a string before serializing it, and then parse the string into a time when you deserialize. Or, to go easier on ...

SF has built in support for static arrays, so u.data should not be a problem. I think all that's missing in your code is an include at the top: