@Wieland Thanks for confirming.

just a push ...

@SGaist Hi, However is in my plan.

The code is good but the comment is false, it's not the parent that will delete socket, it's the event loop at the next occasion.

@raf924 Makes perfect sense, thanks! :)

I woulden't know actually. I think there will be one but why not make it yourself? It's not really complicated. The slaves emit a certain data string to the master indicating them being alive once every 5 minutes for instance. The master keeps track of the slaves and knows when it doesn't receive anything from a slave after 5 mins its offline and perhaps could try to request its status in case the packet got lost or something similar.

I found a solution : I used the waitForReadyRead() function. I still don't know why my code didn't work. Edit : I found that I forgot to connect the slot with the signal, but even with that, it didn't work...

@Pepek said: if (m_uiBlockSize == 0) { if (bytesAvailable < (int)(sizeof(quint64) + sizeof(unsigned char))) return; in >> m_uiBlockSize; in >> m_uiCurrentScanType; //m_timer->singleShot(2000, this, SLOT(resetTCPConnection)); } It's because in unsigned char I have data type that is coming next. I take it into account every time, but truth be told, it is unnecessary to be in header.

@JKSH I tried a few things and it seems it's an access violation error. Normally it should crash but I think it is an unhandled try-catch block. Probably I am going to do the same on this machine too that is, Delete Qt folder manually and install 5.5, and hope that this issue is fixed in the new version :)

Hi @koliva, I have fields to set the IP address [...] I validate if those fields are really IP address using regex Don't do that. QHostAddress::QHostAddress(const QString & address) will do that for you (bool isNull() const). I need to verify also if the given IP address is valid based on given netmask Maybe bool QHostAddress::isInSubnet(const QHostAddress & subnet, int netmask) const does what you want. Btw.: Please don't use special input fields for IPv4 addresses. It's 2015 and all operating systems have IPv6 support. Limiting an application to IPv4 only because of bad GUI design is really stupid.

You should also check the sslErrors signal

Yeah many thanks JKSH it works! Just libeay32.dll and ssleay32.dll are needed. Bye

Hi, One alternative to consider is to rebuild Qt using the new Secure Transport backend for OS X.

@t3685 Yes I'm sure.

I just wanted to tack a me-too on here. I've been converting a QTcpServer app over to 64-bit and it immediately stopped receiving signal. Connecting a 64-bit client to a 32-bit server still worked, so the problem had to be in the 64-bit server or one of the dependencies. As it turned out, the incomingConnection() had an int argument instead of a qintptr, a change we missed when upgrading to Qt5.

Ok, I found my mistake, I was just dumb. I didn't initialize something properly but it looked like it was a bit random so I didnt get it first.

@sergboec Do the numbers come back in a "known" sequence upon each request? IE the first request gives #1, second #2 etc? If so you could still do a single ready read and just have a counter that serves to vector your received data to different handlers.