nanomsg protocols also work with ipc and inproc, so there is a higher level
abstraction here. all that we would need is to decorate UDP to this abstraction
/ interface.
On Mar 25, 2015, at 4:32 PM, George Walker <georgewalkeriv@xxxxxxxxx> wrote:
> Instead of reimplementing those desirable attributes of TCP for UDP, might it
> be less work to take a TCP stack that already runs in userspace and hack it
> to run TCP over UDP?
>
> Sent from my iPhone
>
>> On Mar 25, 2015, at 7:21 PM, Matthew Hall <mhall@xxxxxxxxxxxxxxx> wrote:
>>
>>> On Wed, Mar 25, 2015 at 01:11:31PM -0700, Jay Berg wrote:
>>> "pho-nat" - cool stuff…
>>>
>>> so now i'm wondering if nanomsg high level protocols can be used with a UDP
>>> transport.
>>>
>>> Jay
>>
>> As usual when it comes down to getting things working both in TCP and UDP, I
>> think the answer would be that the effort is non-trivial.
>>
>> TCP features include segmentation, retransmission, reordering, Selective
>> Repeat ARQ, and Path MTU discovery.
>>
>> Performing all of these features in UDP is doable but hardly trivial.
>> It might make sense to see if some features from an RTP stack could be
>> reused
>> to provide these features for nanomsg's use.
>>
>> Otherwise it will be an extremely long road.
>>
>> Matthew.
>>
>>
>
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail
