pdoria
5th September 2008, 11:19
Dear All,
From the fine QT manual:
"This virtual function is called by QTcpServer when a new connection is available. The socketDescriptor argument is the native socket descriptor for the accepted connection.
The base implementation creates a QTcpSocket, sets the socket descriptor and then stores the QTcpSocket in an internal list of pending connections. Finally newConnection() is emitted.
Reimplement this function to alter the server's behavior when a connection is available."
Now the question is:
reimplementing the function prevents the creation of a QTcpSocket? -- meaning that I'm only interested in the socketDescriptor for passing it into another thread and creating the socket there...
Regards,
Pedro Doria Meunier
From the fine QT manual:
"This virtual function is called by QTcpServer when a new connection is available. The socketDescriptor argument is the native socket descriptor for the accepted connection.
The base implementation creates a QTcpSocket, sets the socket descriptor and then stores the QTcpSocket in an internal list of pending connections. Finally newConnection() is emitted.
Reimplement this function to alter the server's behavior when a connection is available."
Now the question is:
reimplementing the function prevents the creation of a QTcpSocket? -- meaning that I'm only interested in the socketDescriptor for passing it into another thread and creating the socket there...
Regards,
Pedro Doria Meunier