You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 22, 2020. It is now read-only.
What steps will reproduce the problem?
1) Send data as fast as possible, insuring that the remote end checks the
integrity of data
2) Once we reach the point where the local buffer is full and Udt::send cannot
send the entire chunk, stream corrupts
What is the expected output? What do you see instead?
Basically the stream when reassembled on the other end has a multiple of
1008-byte chunks missing
What version of the product are you using? On what operating system?
0.7.0.0 on Windows 7 and Windows XP
Please provide any additional information below.
I think this fixes the bug, we need to check to see if the entire chunk was
written correctly:
void NetworkStream::Write(cli::array<System::Byte>^ buffer, int offset, int
count)
{
AssertNotDisposed();
if (!CanWrite)
throw gcnew NotSupportedException("Stream does not support writing.");
int sent = 0;
while (count > 0)
{
sent = _socket->Send(buffer, offset, count);
count -= sent;
offset += sent;
}
}
Original issue reported on code.google.com by daniel.s...@googlemail.com on 6 Aug 2013 at 4:29
The text was updated successfully, but these errors were encountered:
This was resolved in v0.8.0.0, although in a slightly different manner than the
example code. Udt::Socket::Send has been changed so that it blocks until the
entire buffer is sent.
Original comment by cthomas7...@gmail.com on 7 Aug 2013 at 5:01
Original issue reported on code.google.com by
daniel.s...@googlemail.com
on 6 Aug 2013 at 4:29The text was updated successfully, but these errors were encountered: