Search found 238 matches
- Sun Apr 02, 2017 5:45 am
- Forum: Support - RCFProto
- Topic: Unable to load RCF Proto for csharp
- Replies: 3
- Views: 11461
Re: Unable to load RCF Proto for csharp
I just posted in another thread that there is a new build available: Source distribution: http://www.deltavsoft.com/downloads/RCFProto/RCFProto-src-2.3.0.0.zip Win32 binary distribution: http://www.deltavsoft.com/downloads/RCFProto/RCFProto-win32-2.3.0.0.zip With this one you can set maximum message...
- Fri Mar 31, 2017 2:08 am
- Forum: Support - RCF
- Topic: Defending against non-RCF TCP traffic
- Replies: 1
- Views: 9056
Re: Defending against non-RCF TCP traffic
The idle timeouts should be sufficient to drop the connections you are seeing. The idle time is only reset if an actual RCF call is made, so it's unlikely that non-RCF traffic would be able to persist.
- Fri Mar 31, 2017 2:05 am
- Forum: Support - RCFProto
- Topic: Unable to load RCF Proto for csharp
- Replies: 3
- Views: 11461
Re: Unable to load RCF Proto for csharp
Most likely you need to install the Visual Studio 2013 runtimes on your system. The RCFProto Windows binaries are built with VS 2013.
- Fri Mar 31, 2017 2:02 am
- Forum: Support - RCFProto
- Topic: Client-side message length error
- Replies: 5
- Views: 14324
Re: Client-side message length error
OK, I have implemented setMaxMessageLength() on RcfProtoChannel, and built a new release. Source distribution: http://www.deltavsoft.com/downloads/RCFProto/RCFProto-src-2.3.0.0.zip Win32 binary distribution: http://www.deltavsoft.com/downloads/RCFProto/RCFProto-win32-2.3.0.0.zip Please have a go wit...
- Wed Mar 22, 2017 10:05 am
- Forum: Support - RCFProto
- Topic: Compiling error on Linux (OEL 7.3)
- Replies: 1
- Views: 8288
Re: Compiling error on Linux (OEL 7.3)
I'm not sure what's going on there. Can you verify that you have the relevant RTTI compiler flags turned on for all the binaries you are building? If worst comes to worst, you can try commenting out the code that is causing the linker error, in RcfServer.cpp: if (taskEntry.mMuxerType == Mt_None && !...
- Fri Mar 03, 2017 4:36 am
- Forum: Support - RCFProto
- Topic: Compatibily with protobuf version 2.5 and 3.0
- Replies: 2
- Views: 9591
Re: Compatibily with protobuf version 2.5 and 3.0
Hi Sanjeev, It should be compatible, but as we haven't tested, I can't say for sure. Are you using the RCFProto source distribution? If so, you should be able to modify the build so it builds against the relevant version of Protocol Buffers, and then see if any issues turn up. Off hand I don't think...
- Tue Feb 21, 2017 2:57 am
- Forum: Support - RCF
- Topic: Is there any way to allow compression in Publish/Subscribe communication?
- Replies: 1
- Views: 5177
Re: Is there any way to allow compression in Publish/Subscribe communication?
You can use a message filter to compress message data before transmitting over the connection: #include <RCF/ZlibCompressionFilter.hpp> pubPtr->publish().getClientStub().setMessageFilters( RCF::FilterPtr( new RCF::ZlibStatelessCompressionFilter() ) ); Published messages will then be compressed befor...
- Tue Feb 21, 2017 2:49 am
- Forum: Support - RCFProto
- Topic: receive SIGABRT
- Replies: 14
- Views: 30294
Re: receive SIGABRT
Yes that's correct... This is fixed in the latest version.
- Tue Feb 21, 2017 2:47 am
- Forum: Support - RCFProto
- Topic: Pointer to RCF::RcfClient
- Replies: 3
- Views: 11352
Re: Pointer to RCF::RcfClient
Hi Lucimur, Sorry for the late response. You can do this with RCF by creating a RcfClient<> with a UdpEndpoint, passing in a UDP multicast IP. Then when you make a remote call on the RcfClient<>, the message will be broadcast on the UDP multicast IP. To use protobuf messages, generate C++ code for y...
- Tue Feb 21, 2017 2:40 am
- Forum: Support - RCFProto
- Topic: Async RCFProto Example
- Replies: 3
- Views: 11095
Re: Async RCFProto Example
Async client calling doesn't need any changes on the server side, as it's entirely a client-side technique. For async server-side dispatching, you would preserve the RpcCallback object you receive from Protocol Buffers, store it in a list somewhere, and a worker thread would then pick it up and even...