Sorry it took so long for this post, other things intervened. Anyway, quick
responses to the three people who commented.
Shulhan, there is a better mechanism in Go than resetting the buffer. Have
a second variable, say "var message []byte", and then after the call to
ReadMsgUDP add this line "m
I am not sure that is the case. It is “known” that UDP doesn’t support OOB,
mainly since it is not a stream - it is packet oriented, but also because it is
not part of the specification - it would have to be an application level
transport that adds that as far I understand.
That being said, I a
Thanks, that makes sense. So the documentation here needs some work since
that is not at all clear.
On Sunday, April 7, 2019 at 11:42:52 AM UTC-4, Pelle Johansson wrote:
>
> Hi John,
>
> The oob data used in these system calls are not for communicating with the
> peer. UDP doesn't support OOB d
Hi John,
The oob data used in these system calls are not for communicating with the
peer. UDP doesn't support OOB data on the wire, I think the name here is a
bit unfortunate, it should rather be called "control" or somesuch. This
data is processed/created locally by the kernel and its structur
