Listening and receiving data from a socket.

[SPlatten]

@JonB , how the data is received is nothing to do with how it is sent, I can receive the same data as either a QString or array, the content is the same. I've also tested the same code using a QString, the result is the same.

What I mean by this is that receiving data in a QByteArray or QString makes no difference, the content would be the same, the only difference is the way 0 (nulls) are handled.

[JonB]

@SPlatten
You are failing to understand. Nothing to do with QByteArray vs QString.

how the data is received is nothing to do with how it is sent

Not at all true, given that you are using QByteArray, and transactions. How it is sent totally does matter. Nothing other than client sending a QByteArray via a QDataStream will satisfy your server receiver code. You are thinking, somehow, that bytes sent without QDataStream can be received as QDataStream, which they can't.

I have typed in a detailed explanation in an EDIT to my previous to try to help you. Until you understand that you are going to struggle, I urge you to read it carefully.... :)

[SPlatten]

@JonB , It was my understanding which is obviously wrong that I could receive any data on the socket using a QDataStream, in my testing I'm trying to receive data from a browser which is a standard HTTP request.

I'm now replacing the QDataStream receive data with:

void clsListener::onDataIn() {
    QByteArray arybytMsg;
    while( mpClient->bytesAvailable() ) {
        QByteArray arybytMsg = mpClient->readAll();
        qdbg() << "HERE";
    }
}

Just to see if that resolves the issue.

[Edit] This now works and I am receiving the data.

[Christian Ehrlicher]

@SPlatten said in Listening and receiving data from a socket.:

It was my understanding which is obviously wrong

It's all in the docs: "A data stream is a binary stream of encoded information..."
It really helps (as already told you many times) to read the documentation of a class before using it.

[SPlatten]

@Christian-Ehrlicher , thank you, that just takes time which I don't feel I have.

[Christian Ehrlicher]

@SPlatten said in Listening and receiving data from a socket.:

that just takes time which I don't feel I have.

You would have solved the issue by yourself 17hours ago when you would have read the documentation.

[JonB]

@SPlatten
This is getting better, but you are still assuming that one readyRead call to onDataIn allows you to write a loop on bytesAvailable() and that will accumulate all bytes sent. It won't. It may do because your message data is so small, but not necessarily, and not if the data gets larger. (Try sending a very long [e.g. many K? megabytes?] string!)

I showed you the only correct algorithm. Save the data received into a persistent (e.g. member variable) buffer. Append to that as more arrives. Check if you have now received the terminating } from your sending "protocol". When you do, you have the complete message. Period.

[KroMignon]

@SPlatten said in Listening and receiving data from a socket.:

how the data is received is nothing to do with how it is sent, I can receive the same data as either a QString or array, the content is the same. I've also tested the same code using a QString, the result is the same.

That's not true, you have to read data in the same way you sent them when you are using QDataStream.
As TCP is a stream socket, you can not be sure all data have been received, so startTransaction() in combination with commitTransaction() will simply reception side. When not all data are received, QDataStream will rollback the readed data and so you can retry reading on next received data chunk.

But to ensure this works, you have to read what you have transfered, in the same order.

[jsulm]

@SPlatten said in Listening and receiving data from a socket.:

that just takes time which I don't feel I have

But you have time to ask in a forum and wait for an answer?!

[SPlatten]

@jsulm , whilst I try to resolve it myself, granted I could also be reading the documentation.