Delta V Software Forums

Hi Joel, The intent of the code is to create one deadline timer object for each callback connection, lasting for the duration of that connection. So if you are seeing deadline timers created for each read/write that's a definite bug... Is that what's happening in your program? I think associating th...

You only need the Boost headers. So all you need to do is download Boost, unzip it somewhere, and then set your compiler include path so it can find the Boost headers.

Hi Konstantin, The publish/subscribe implementation in RCF does not support UDP. What you can do with UDP, though, is to make use of multicast and broadcast addresses to setup a much simpler publish and subscribe system, as described here: http://www.deltavsoft.com/doc/rcf_user_guide/Transports.html...

The third parameter to enableLogging() is the log format string, which allows you to customize the fields that are printed to the log. I see we've missed documenting the format of that string, but here is a list of the format specifiers that are available: %A: Log name %B: Log level %C: Time %D: Thr...

There isn't currently a built in way to iterate over all existing client connections, but as your server is in C++, you can use regular RcfServer functionality to accomplish this. For each client connection, you should create an application-specific session object, as described here: http://www.delt...

Unfortunately it's currently not possible in RCF to set socket options before the socket is connected... I'll put a fix in for that for the next release, and for now you'll have to modify the code itself to set this option. For client side code, you'll want to modify TcpClientTransport::setupSocket(...

Have you had a look at the logging support in RCFProto:

http://www.deltavsoft.com/RCFProto/doc/ ... gging.html

You can experiment with logging levels to find the level that suits you.

Sorry, this is currently not possible... However it is high up on the list of features we are looking to implement.

You can do regular RCF file transfers, if you are using C++ bindings on both client and server ends - however I'm guessing this is not the case in your situation.

Hi, RCF suppports HTTP, including the use of HTTP proxies. So what you can do is use a HTTP transport to connect from your clients to the main server, and this will allow you route client requests through an HTTP proxy in each local group. Here is some more information on HTTP support in RCF: http:/...

There should be an assert message in the output window of your application, when this happens - can you send that to us.

Is there a way of reproducing this?