Reliable UDP?
Posted: Tue Sep 09, 2014 12:22 am
Hello,
Thank you for providing support.
First off, I have some confusion whether RCFProto actually supports the UDP transport.
It is not advertised here http://www.deltavsoft.com/RCFProto/distro/index.html
BUT, the doc alludes that UDP may be supported: http://www.deltavsoft.com/RCFProto/cpp/ ... point.html
So, assuming the UDP is supported, is reliable UDP supported "in the box"? By reliable UDP, I mean Adaptive retransmission timeouts with ACKs at the minimum, perhaps message sequencing on top of that, and multiplexing channels on a port would be "extra." ENet (http://enet.bespin.org/) provides all of the above, and I could consider throwing it atop RFC. But at that point, why not use Google Protocol buffers with ENet exclusively? <-- that's the main point of my dilemma
Let me provide a very brief history:
I have been searching for a nice multi-platform C++ library for networking applications. I want multi-language serialization solution (Google Protocol Buffers) and will be using both reliable UDP and raw UDP. I have already created a homebrew implementation of reliable UDP and serialization, but it's not what I want. Moving to protocol buffers at least begins support for non C++ languages. RFC came to my attention thru the Google Protocol Buffer 3rd party page. Then I thought, hm, I wonder if RCF can clean up my implementation and prevent me from having to mix several libraries together? But I'm not sure I can do that without the reliability over UDP. And I'm too tired to analyze RFC docs to find out. So in a way this is a chance to win me over by talking about some really cool features of RFC that might interest me because I am just too damn tired to look myself.
Thank you,
Bazz
Thank you for providing support.
First off, I have some confusion whether RCFProto actually supports the UDP transport.
It is not advertised here http://www.deltavsoft.com/RCFProto/distro/index.html
BUT, the doc alludes that UDP may be supported: http://www.deltavsoft.com/RCFProto/cpp/ ... point.html
So, assuming the UDP is supported, is reliable UDP supported "in the box"? By reliable UDP, I mean Adaptive retransmission timeouts with ACKs at the minimum, perhaps message sequencing on top of that, and multiplexing channels on a port would be "extra." ENet (http://enet.bespin.org/) provides all of the above, and I could consider throwing it atop RFC. But at that point, why not use Google Protocol buffers with ENet exclusively? <-- that's the main point of my dilemma
Let me provide a very brief history:
I have been searching for a nice multi-platform C++ library for networking applications. I want multi-language serialization solution (Google Protocol Buffers) and will be using both reliable UDP and raw UDP. I have already created a homebrew implementation of reliable UDP and serialization, but it's not what I want. Moving to protocol buffers at least begins support for non C++ languages. RFC came to my attention thru the Google Protocol Buffer 3rd party page. Then I thought, hm, I wonder if RCF can clean up my implementation and prevent me from having to mix several libraries together? But I'm not sure I can do that without the reliability over UDP. And I'm too tired to analyze RFC docs to find out. So in a way this is a chance to win me over by talking about some really cool features of RFC that might interest me because I am just too damn tired to look myself.
Thank you,
Bazz