QTcpSocket and QProgressBar/QProgressDialog

[wysota]

Yes, theoretically I understand how I need to calculate, but my question was how!? May be some signals?

It depends how you do the reading. The most basic aparatus you have is bytesAvailable().

I'm afraid I have to use QDataStream because I need to transfer complicated data structure (QList) via socket, and for this small app no reason to make my own functions.

You don't need QDataStream for that.

I think the speed issue did not correlate with QDataStream, my be with some settings, memory pre-allocation but not with QDataStream itself.

Data transfer time over network is directly proportional to the amount of data being transfered. The less data to transfer, the less time it takes.

[nikkadim]

It depends how you do the reading. The most basic aparatus you have is bytesAvailable().


You don't need QDataStream for that.

Do you have link to some code example for this?
PS: Now I have receiving speed about 20 Mbit/s, at 1Gbit/s NIC. Test was performed on one machine.

[wysota]

Do you have link to some code example for this?

No, I don't have link to any example code If you want an efficient protocol, it has to depend on what you are currently doing.

The most trivial (but probably not a very clever) approach would be to simply memcpy() your structure to the socket and then do the same on the other end.

PS: Now I have receiving speed about 20 Mbit/s, at 1Gbit/s NIC. Test was performed on one machine.

I don't see how that's relevant to anything. Especially if you are sending to localhost which doesn't even use your network interface card.

Either you have efficiency or ease of use. Choose which is more important for you.

[nikkadim]

Looks like you recommend me don't use QT at all

[wysota]

No, I recommend you to use tools and mechanisms proper to the problem you are facing. I understand you took the code from some Qt example (e.g. fortune cookie) but this is very generic (and badly written) code that is not suited for problems more complex than reading a couple of bytes from the socket. If you know what structure of data you expect, then you really don't need to send the size of that structure to the socket and you don't need to go through generic serialization code that sometimes bloats the data sent unnecessarily (and obscures access to the data from non-Qt applications).