Data splitting and merging about kcp-go HOT 6 OPEN

You can encode like this: |size|payload| , try to add a size prefix before the payload.

from kcp-go.

I don't quite understand what you mean, can you tell in which method this parameter should be set.

from kcp-go.

why not just add a prefix before the data, the prefix suggests how many bytes are there in the packet.
|size|payload|size|payload|.... |size|payload|

from kcp-go.

Do you mean that before calling the Write method, I split the binary data myself, and each split data packet needs to add a 2-byte prefix to indicate the size of the data packet?

In fact, my core question is whether the work of splitting data packets is implemented in the third-party package or by the user himself?

from kcp-go.

users should be in charge of managing the border of packets. In general, kcp-go provides a realiable stream only.

from kcp-go.

When I looked at the code, I found that you would split the large data packets into segments, so I thought that the third-party package had already encapsulated the data splitting work.

Because after I modified this code, when sending a large data packet, the simulated client can normally receive a complete assembled data packet, so I think that this data splitting work needs to be encapsulated, and the user is not responsible for managing the boundaries of the data packet.

So if I make the above changes, will there be any serious consequences?

from kcp-go.