Delta V Software Forums

For an RCF server, synchronous and asynchronous calls look exactly the same. So if your server needs to treat these two situations differently, you'll need to add the information into your remote calls, either as extra parameters in your remote methods, or by setting some custom user data in your re...

Boost.Serialization is still supported, but at the moment if you want to build with B.Ser. you will need to disable the recently added proxy endpoint feature, as that has a dependency on SF serialization. So in your build you should define these: RCF_FEATURE_BOOST_SERIALIZATION=1 RCF_FEATURE_PROXYEN...

You can pass binary blobs back and forth on a RCF connection, using RCF::ByteBuffer: http://www.deltavsoft.com/doc/_performance.html ByteBuffer's are never copied, they are only reference counted, so you can move a lot of data around without incurring significant overhead. If you have a method like ...

Hi there, Polymorphic serialization with Boost is a tricky area, and my recommendation would be to use SF instead, as I think it's much more straightforward. If you have to use Boost, I think you'll need to register the derived class so that Boost.Serialization knows about it ahead of time. In some ...

Hi,

Once a RcfClient<> object has connected to a server, you can retrieve the socket handle, and then use that to set socket options:

http://www.deltavsoft.com/doc/_transpor ... cketAccess

Currently you can only have one topic per subscription.

Here is a link to the latest download with a fix for the runtime error:

http://deltavsoft.com/downloads/RCF-3.1.301.zip

Hi there, For the first issue, with getSubscriberCount() returning 0, I'm unable to reproduce it in my test code here. One thing you could try though is to publish a ping to all subscribers, before getting the subscriber count: PublisherPtrptr.publish().getClientStub().ping(); , and see if that make...

Hi, There isn't anything on the server-side (i.e. publisher-side), that would allow publishing to select subgroups of subscribers, within a topic. You could instead include some information in the published messages, and then let the clients use that information to determine if they should ignore th...

Hi,

This is to be expected when when lots of short-lived TCP connections are being created, and it's due to how TCP is implemented in the operating system. There are various ways to work around it, for example have a read of this:

https://www.fromdual.com/huge-amount-of ... onnections

Hi Dave, At this point it doesn't look like we can implement multiple outstanding requests on a single connection, because it would break the HTTP tunneling feature. The HTTP protocol does not allow multiple outstanding requests in general (there is the 'pipelining' hack but it's pretty limited and ...