QTcpSocket / QTcpServer, connection closed

[SPlatten]

@jsulm ,@KroMignon , sorted, it's now working and communicating, thank you:

void clsSocketServer::incomingConnection(qintptr sfd) {
    clsSocketClient* pClient = new clsSocketClient(new QTcpSocket());
    pClient->setSocketDescriptor(sfd);
    addPendingConnection(pClient);
}

[KroMignon]

@SPlatten said in QTcpSocket / QTcpServer, connection closed:

class clsSocketClient : public QTcpSocket {
Q_OBJECT

public:
    explicit clsSocketClient(QTcpSocket* pClient = nullptr);

...

Please change this to:

class clsSocketClient : public QTcpSocket 
{
    Q_OBJECT
public:
    explicit clsSocketClient(QObject *parent = nullptr);

[jsulm]

This post is deleted!

[KroMignon]

@SPlatten said in QTcpSocket / QTcpServer, connection closed:

void clsSocketServer::incomingConnection(qintptr sfd) {
clsSocketClient* pClient = new clsSocketClient(new QTcpSocket());
pClient->setSocketDescriptor(sfd);
addPendingConnection(pClient);
}

Why to you do this?
clsSocketClient* pClient = new clsSocketClient(new QTcpSocket()); is an nonsense!

[jsulm]

@SPlatten said in QTcpSocket / QTcpServer, connection closed:

which is derived from QTcpServer

QTcpServer != QTcpSocket

[SPlatten]

@KroMignon It compiles and works, I tried several other things that don't.

[jsulm]

@SPlatten said in QTcpSocket / QTcpServer, connection closed:

It compiles and works

Doesn't change the fact that it is nonsense.
Do it the way @KroMignon shown you.

[SPlatten]

@jsulm , @KroMignon , changed and compiled, still working :)

[KroMignon]

@SPlatten said in QTcpSocket / QTcpServer, connection closed:

changed and compiled, still working :)

It is really disappointing that you don't try to understand what you are doing wrong.
This give the bad taste that you are just placing code together but not have a clue what you are doing.

The class constructor QTcpSocket(QObject *parent) is used to define the parent object to this instance.
Parent is used, in Qt, to handle automatic instance cleanup when parent instance is destroyed.
This simplify also threading, moving parent instance to a thread will also moves all his "childrens".

• https://doc.qt.io/qt-5/object.html
• https://doc.qt.io/qt-5/objecttrees.html

Please, please, read a little bit of Qt documentation to understand what you are doing.

By doing clsSocketClient* pClient = new clsSocketClient(new QTcpSocket()); you a creating a class which will have a parent QObject, but for what?

And the QTcpSocket instance you have created will never be deleted!!!

This not clean programming!

[JKSH]

@SPlatten said in QTcpSocket / QTcpServer, connection closed:

the samples FortuneServer and FortuneClient do not use incomingConnection directly either, they are very lean examples. The examples to not call addPendingConnection either.

The important difference here is that the FortuneServer example does not subclass QTcpServer or QTcpSocket. When you subclass it and reimplement functions, there are more gotchas to watch out for.

Your program looks quite complex; I suggest you start by implementing a simple "lean" program from scratch first (without subclassing) and make sure that works. After that, you can gradually add the extra features that you want.

[SPlatten]

@KroMignon , How can you possibly know what I'm trying to do, of course I want to understand it.

The issue is I have such a lot of work ahead of me that I just don't have the luxury of spending hours on one particular problem.

[SPlatten]

@JKSH The intention is that any complexity is hidden and the end result is much cleaner and easier to use.

[KroMignon]

@SPlatten said in QTcpSocket / QTcpServer, connection closed:

The issue is I have such a lot of work ahead of me that I just don't have the luxury of spending hours on one particular problem.

In french we say "Il ne faut pas confondre vitesse et précipitation!", could be translate with "Speeding up is not the same as rushing. "

We don't have the same perception about "losing time".
I believe that spending 5~10 minutes to understand the Qt "basics" will helps you to save even more time later to not have to undo and redo what you have done and not works properly.

But this is up to you, which you good luck for your development.

[JKSH]

@SPlatten said in QTcpSocket / QTcpServer, connection closed:

@JKSH The intention is that any complexity is hidden and the end result is much cleaner and easier to use.

I was referring to the complexity of your implementation. Its complexity made it hard for you to understand where your errors were coming from.

I believe you'll have better success in the future if you start learning a new class by implementing simple and "lean" code from scratch first, make sure it works correctly first, and then gradually add more features on top.

Furthermore, you can hide complexity without subclassing/inheritance. You could hide the QTcpServer as a member variable of another class instead. We should often prefer composition over inhertance -- If you took this approach, you wouldn't have needed addPendingConnection()and you would've avoided the issues you raised in this thread.

I have such a lot of work ahead of me that I just don't have the luxury of spending hours on one particular problem.

Please understand: @KroMignon's concerns are not specific to this particular problem. He's asking you to develop an understanding of some foundational concepts of C++ and QObjects which apply to most of your code -- not just TCP-related code.

Do you understand now? In this line clsSocketClient* pClient = new clsSocketClient(new QTcpSocket()); :

1. What does new clsSocketClient() do?
2. What does new QTcpSocket() do?
3. What happens when you pass new TcpSocket() into the constructor of your clsSocketClient?
4. What happens when you pass nullptr into the constructor of your clsSocketClient?