🚀 go-pugleaf

Michele Santucci wrote:

> anyway I fixed my problems rigth now but I noticed a strange behaviour...
> I set up my ServerSocket to be stNonBlocking so when the client sends a 
> packet to my server the ClientRead event is fired.
> Inside my OnClientRead event handler I start reading bytes of the message 
> using the ReceiveBuf socket method.

You should alway read exactly the amount of bytes indicated by
Socket->ReceiveLength(). If that gives 0 of < 0 then return.

> Anything works here but if I call Application->ProcessMessages() somewhere 
> in my code before having completly unbuffered received data the OnClientRead 
> event is fired again...
> That sounds pretty strange to me.

What do you mean with "completly unbuffered" ?

It is better not to call ProcessMessages with a non-blocking socket
is my experience. It makes no sence too. If you received all bytes
indicated by RecieveLength() and handled the data then the
function ends and so the application can process messages without
you having to tell to do so.

Hans.