C / C++ / MFC

(int)strlen(message), // Length of data

if(astr.Set(szBuf))

Archyami wrote:

I tried to send "strlen(message) + 1" bytes to the server.
The exception appears less often, but still occurs

szBuf=(char*)malloc(sizeof(char)*(CATOS_BUFFER_SIZE+1));

int TotalBytesReceived = 0;

while (TotalBytesReceived < CATOS_BUFFER_SIZE)
{
	int CurBytesReceived = ::recv(theSocket, &szBuf[TotalBytesReceived], CATOS_BUFFER_SIZE - TotalBytesReceived, 0);
	if (CurBytesReceived == 0)
	{
		// connection gracefully closed!!
		break;
	}
	else if (CurBytesReceived == SOCKET_ERROR)
	{
		int rc = WSAGetLastError();
		if (rc != WSAEWOULDBLOCK)
		{
			break;  // socket error occurred!!
		}
	}
	else
	{
		TotalBytesReceived += CurBytesReceived;
	}
}

if (TotalBytesReceived == CATOS_BUFFER_SIZE)
{
	// Successfully received CATOS_BUFFER_SIZE bytes
	//do something with szBuf
}
else
{
	// something happened before we received CATOS_BUFFER_SIZE bytes
}

Archyami wrote:

1. The message eg. equals "abc". Its length is 3.
Why should I send its length as 4?
(The server is checked to send data within the length of CATOS_BUFFER_SIZE.)

Archyami wrote:

2. The recv buffer is allocated with 1 more byte for safe (may be it is a risk...)
My design is that if CATOS_BUFFER_SIZE==10 and message comes from the server as "1234567890", it can hold the message. Indeed, a terminator is at the end (here is '0'). If '\0' is padded by the server, it can still hold the message.
'\0' is padded automatically for initializing an char array.
Please advise if my analysis is wrong.

Archyami wrote:

3. If the server is checked to send data within the length of CATOS_BUFFER_SIZE, is it possible that the client recv() may receive the message sereral times instead of once?
I mean: recv() holds the application (thread). 'several times' refers to 1 recv() receives a part of the message, several recv() receives all message 'packages'.

li zhiyuan wrote:

how to add a class which don't attach .cpp and .h files?