How to split a large data into chunks while using websocket in C#?

Question

0.00/5 (No votes)

See more:

, +

I want to split a buffer of a large data into chunks while using websocket in c#.

I am trying to send over a web socket but I am not getting the entire data.
byte[] buffer = encoding.GetBytes(stringtoSend); I want to split it as chunks to the server side from client.

What I have tried:

Core Code is as below:

byte[] buffer = encoding.GetBytes(stringtoSend);

                   bool EndofMessageStatus = false;



                 await webSocket.SendAsync(new ArraySegment<byte>(buffer), WebSocketMessageType.Binary, EndofMessageStatus, CancellationToken.None);

Posted 16-Jul-18 20:16pm

ranio

Updated 16-Jul-18 21:35pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Jochen Arndt · Answer 1 · 2018-07-16T21:36:00

If you have problems at the receiving side, sending data in chunks will not solve them. It will make your code more complex and might introduce new problems.

Try to solve the receiving problems instead.

I can only guess here:
You are sending a string and have problems to detect the length when receiving. Then send the length of transferred data first followed by the payload. So the receiver knows how many data he has to receive. Defining such is called a "protocol" and common for socket communications.