MG_IO_SIZE

[lonejack]

Hi,
I'm running mongoose for a mqtt test on linux as client.
The version used is 7.13. 52997c6
For this implementation I started from:
examples/mqtt-client

The problem faced.
When I exchange messages with broker I'm allowed to see messages where the length in term of size is less than MG_IO_SIZE.
I I want to receive messages much larger I've to modify the MG_IO_SIZE parameter.

On the documentation I see the meaning of the parameter:
MG_IO_SIZE Granularity of the send/recv IO buffer growth

To me seems that if you have to receive a greater message the mongoose provide to enlarge automatically the buffer.
Am I right?
Currently I changed the parameter from 2048 to 16384 and it works...

[scaprile]

Mongoose resizes its buffer in MG_IO_SIZE-size chunks up to MG_MAX_RECV_SIZE.

mongoose/mongoose.c

Lines 7386 to 7397 in 497df68

	static bool ioalloc(struct mg_connection *c, struct mg_iobuf *io) {
	bool res = false;
	if (io->len >= MG_MAX_RECV_SIZE) {
	mg_error(c, "MG_MAX_RECV_SIZE");
	} else if (io->size <= io->len &&
	!mg_iobuf_resize(io, io->size + MG_IO_SIZE)) {
	mg_error(c, "OOM");
	} else {
	res = true;
	}
	return res;
	}

It is very hard for me to guess what is going on with such a description. What exactly happens ?
Please sniff your network (using Wireshark, for example) and observe the traffic.
Please see the logs.
What fails ? When ? Where ?
If, after your network inspection, you find an actual issue, feel free to open an issue, fill the issue template, and provide us with pertinent information (including useful network captures) in order to reproduce and fix the issue. We don't inspect your code for errors, please send the minimum piece of code that can reproduce the issue