RoganDawes

To be clear, I am also only getting about 4kbytes/sec using my implementation. I *suspect* this is because of shoddy powershell code (or my Java-side code, possibly), or because of...

What gets interesting is adding a Write statement into the powershell after $d.Write(), that writes the received bytes back to the device, then updating the command on the pi to:...

The easiest way to deal with this is to make sure that the Windows side does the first write, always. This lets you be sure that the remote end is...

And this code, while not beautiful by any means, gets reasonable performance, while not losing any data! ``` $M = 64 $cs = ' using System; using System.IO; using Microsoft.Win32.SafeHandles;...

If you look at my Powershell second stage, I use async calls (BeginRead, et al) to avoid blocking (and to be able to deal with reading from the sockets/shell as...

I was thinking of something similar, multiple threads doing blocking calls on whatever source (Accept, or Read calls on sockets or devices). My puzzlement is with regards to communicating between...

Nice work! As you can see, I am implementing the same idea both on AVR/ESP and Linux, so we can continue to collaborate ;-) For the moment, I'm happy with...

The continuous alternating read/write effectively halves your throughput, which you can recover by doubling the number of end points. An alternative is to simply reduce the number of acknowledgements required....

Yes, indeed, you are absolutely right, that there is no need to flush the P-ACKs. As you have observed, I am modelling my protocol on TCP, so I'm not sure...

I struggle to believe that BeginWrite/EndWrite on a MemoryStream is necessary, or even efficient. Unless you are doing it to be compatible with Async operations on other types of streams,...