🚀 go-pugleaf

I know, I am using them, but I'm just wondering if there was already
something that could help me in this situation..

I'm sending binary data.
Each message's first bytes contain the size of the message. I only receive
about 50k at once, so my code in OnRead is called many times. It ends the
recording and processes the message after all the data it was told it was
getting has been received.

If it is one byte too long or short, it's fatal.
Is there a way for it to be too long, and is there a way it could be too
short other than the client suddenly disconnecting in the middle of the
transaction, and would that cause throw an exception?

I could use a timer that would count how long the socket has been idle, if
all the message isn't received, I end the message, but if there is a lot
messages being received it wouldn't work.

Many times I send the header to the message before the rest of the message
too, (this way I dont have to copy a LOT of data to a new buffer just to
send it, it would be dreadfully slow), is that dangerous?

I'm kinda stuck here....
Please help
Thanks.