This is more a question than anything else

[Giszpenc]

I tried using your code and it worked fine until I changed it to work with my real data and found that I was losing packets. In my scenario, I work with devices listening on some port. I send a request on the broadcast ip (255.255.255.255) on that port and wait for each device to say hello back (on my desktop) same port. So I am mixing a client and server in one which might be a threading problem. This works with a couple of devices but with a couple hundred devices, I am losing many responses.

I am curious if you are planning to use System.IO.Pipelines. It seems that it might be faster at consuming data off the wire and adding it to be consumed by a reader later when it is ready.

[sgf]

Pipelines are not really suitable for UDP. If you are experiencing packet loss, then you should consider looking into an R-UDP protocol. Or implementing your own.