Delta V Software Forums

Yes, you will generally need to have WIN32_LEAN_AND_MEAN defined, when building on Windows. In build 2664, I've changed the error message that emanates from Boost.Asio, to indicate this. The easiest way to deal with this is to specify WIN32_LEAN_AND_MEAN in your build settings (pass -DWIN32_LEAN_AND...

Thanks for your feedback. The request id issue comes down to a limitation in JSON Spirit, the library we are using to parse JSON-RPC requests. Basically it will fail to parse a JSON-RPC request if the request id is not a number. I would suggest reporting this to the JSON Spirit author here: http://w...

I will add it to the todo list - thanks for the suggestion.

We are pleased to announce the release of RCF 2.0. You can download RCF 2.0 here: http://www.deltavsoft.com/download.html As part of the 2.0 release, we have also reworked the RCF User Guide: http://www.deltavsoft.com/doc RCF 2.0 has a number of syntactic changes from RCF 1.3.1, however almost all f...

A RCF 2.0 release candidate is now available on the Download page.

A release candidate for RCF 2.0 is now available on the Download page.

A preliminary version of the RCF User Guide for 2.0 is available here.

Unless breaking issues are encountered, we anticipate releasing RCF 2.0 shortly.

Thanks for the explanation Glad you got it working.

Hi Volker,

I don't have a dev environment with gcc 4.7.0 readily available to test on. However - do you get still get the error if you omit the "-stdc++0x" flag?

We're hoping to have a release this month. The codebase is ready to go on pretty much all platforms, and we are currently working on finishing the documentation.

I have one function on the server side that needs to know a caller identifier. Depending of the client who is calling this function, the result will differ. Is there a way to identify the client, from a function located in the server side ? When the client connects, you can have them pass a client-...