Multiple TcpClients to multiple Servers

[ChrisW67]

TcpClient::ReadTcpData(), Connected(), Disconnected() and ErrHandler() are declared as signals not slots: you do not provide implementations for signals because they are generated by moc. I think you intend these to be slots based on earlier attempts to connect to them as slots.

[sa5webber]

You're absolutely right. Thanks so much for taking the time to look at it.

I have another question if you don't mind. In the TcpClient class readyRead() signal is there a way of sending the client socket connection that received/generated the readyRead() to the slot that receives the signal? In other words I would like to have a common slot routine which not only reads the receiving message but knows which server connection it received the data on for communicating back to that server. As I have it now each TcpClient connection has its own slot routine and from this I was planning on emitting/relaying the client connection and data to the subscriber. Is what I'm doing the best way of accomplishing what I want?

Also if I continue with my current approach, I would like to connect, I guess effectively signals from each TcpClient object to a slot in MainWindow. Does this have to be relayed or re-emitted through ConnectionMgr or is there a more efficient way to connect directly to emits from the TcpClient to slots in the MainWindow.

Thanks again for your time.

[ChrisW67]

There is no TcpClient::readyRead() signal declared that I can see. Assuming you mean readyRead() emitted by TcpClient::_tcpClient then you can connect it to a slot in TcpClient that simply emits a signal, defined on TcpClient, that carries the TcpClient address to any listeners. Passing the QTcpSocket's address would allow external access to the private member variable: possibly not a good idea..

[sa5webber]

Yes the readyRead() signal is not defined in TcpClient.h segment here. When I entered this listing I was still trying to resolve the errors I had asked about with this listing which as you pointed out was due to me still getting my head around the signal/slot naming convention. That mistake has definitely made that clearer to me.

In any event I have what I was asking about working with the ConnectionMgr receiving and re-emitting each of the TcpClient signals to the MainWindow. So in this case I might have actually answered my own question. Again I can't tell you how much I appreciate and admire all of the help people like you provide to this forum. I'm sure I'll have other questions as I forage my way through QT. Thanks for being there.