@AJ_Oldendorf i am no expert in
Indy at all, as i hate the s*** out of it due to
exception raising policy, but while waiting for someone to resolve this for you, let me put few thoughts
1) Make sure you are blocking on the socket means as long you existing the loop then it will return and this will raise the CPU usage up to full Thread/Core.
2) ReadLn is blocking capable and that why it used everywhere.
3) Guess what ?!
ReadBytes also blocking capable too.
so try this
Delphi-Quellcode:
procedure TMyTCPServer.OnExecuteHandler(AContext: TIdContext);
var
Buffer: TIdBytes;
begin
if not AContext.Connection.Connected then
Exit;
AContext.Connection.IOHandler.ReadBytes(Buffer, -1, True); // block and wait ! , while True for append (best practice) in case there is leftover
if Length(Buffer) > 0 then
FDataQueue.Enqueue(Buffer);
{
//SetLength(Buffer, 61000); //<- nicht feste größe einlesen
while not AContext.Connection.IOHandler.InputBufferIsEmpty do
begin
SetLength(Buffer, AContext.Connection.IOHandler.InputBuffer.Size); //<- so viel einlesen wie im Buffer enthalten ist
AContext.Connection.IOHandler.ReadBytes(Buffer, Length(Buffer), False);
FDataQueue.Enqueue(Buffer);
end;}
end;
On side note this blocking might need timeout adjustment, so adjust AContext.Connection.IOHandler.ReadTimeout to something short, it could be 30 second or even shorter will be fine, this might affect how much concurrent connection you expect, if few then put it 1 second (timeout = 1000) and it will be find.
about the hate for
Indy, it comes form where an
exception will surprise you, well from almost every line/operation, so i think some try..except is due somewhere in your client and server, but again you need someone else to help with what i wrote (which could be not the optimal) and
exception handling..... or
Try somethin else ICS has plenty of examples/samples and it is way more friendly with its events,
Indy still valuable and will stay the most protocol stuffed library in pascal.