Indy icon indicating copy to clipboard operation
Indy copied to clipboard

Expose direct buffer send/receive

Open gec75 opened this issue 1 year ago • 1 comments

I have a special device which has a high data throughput... For this case, I want to bypass all internal buffering (I have my own simple line handling) and use low level socket select/send/receive. But currently Send/Receive only work via TBytes. I can reach hundreds Mb/s... even though the PC can handle that, I want to avoid intermediate copies.

Currently I use TIdSocketHandle (after connect), but have to hack via TIdStackBSDBase.WSRecv...

Is there a reason NOT to allow direct buffer access? It would be an easy interface addition with overloaded functions...

indy_ll_buffer.patch

gec75 avatar Apr 26 '23 07:04 gec75