QTCP server ... possible run more than one?

[gfxx]

@jsulm because I share data per client request and data need to go to that client .... so for know what type of data need to send, need to know if that client is connect or not .... plus when receive data need to know witch client send that data .... because packet not contain client id so not possible filter it ....

Sorry but for me socket is a quite new affairs ....

[gfxx]

@Christian-Ehrlicher .... you are in right

[gfxx]

@jsulm for me is almost all new ..... so how can i figure out which client machine connected? .... auto reply: if build a sokClass and new istance of class every newconnection .... no need to know that .... so

void MainWindow::initServer(){

    server = new QTcpServer(this);
    client = new Sokclient();
    client1 = new Sokclient();
    client2 = new Sokclient();

    if (!server->listen(QHostAddress("192.1xx.xx.xxx"), xxx)){
        QString ipi = "no connection";
        //return;
    }
    else{
/****  these is all wrong .... how can connect nexpendingconnection to new SockClient class object client, client1 and client2?? *****/
        //connect(server, &QTcpServer::newConnection, this, [=](){client = server->nextPendingConnection(); new_con(); qDebug() << " connect ";});
        //connect(client, &QTcpSocket::readyRead, this, &MainWindow::readSocket);
        //connect(client, &QTcpSocket::disconnected,this, &MainWindow::discardSocket);
        //connect(ui->pbtn_F_send, SIGNAL(released()), this, SLOT(sendOrder()));  

then need connect mainwindows signal to SokClient class slot ....

[jsulm]

@gfxx said in QTCP server ... possible run more than one?:

when receive data need to know witch client send that data

You know from which client you got data because for each client you have a dedicated QTcpSocket instance (as I already wrote above). So, you simply write to the same socket from which you got data...

[gfxx]

@jsulm sorry non understand ...

connect(server, &QTcpServer::newConnection, this, [=](){client = server->nextPendingConnection()

call "client" on mainwindows ...... next connection can't be "client" .... at least need to be "client2" ..... how can i pass server->nextpendingconnection once to client2, then to client3 etc etc??

[Christian Ehrlicher]

Again: create a worker object which handles each connection for you, store the worker objects in a container if you really need to access them from anywhere else. Learn basic c++ principles.

[jsulm]

@gfxx said in QTCP server ... possible run more than one?:

next connection can't be "client" .... at least need to be "client2"

Nothing stops you from storing all the QTcpSocket instances in a container (like QVector for example), like @Christian-Ehrlicher suggested already...

[gfxx]

@jsulm thanks .... but these means every time need one istance need to choose the right from qvector ... or qlist or other container .... so problem is almost the same .... why start soket1, soket2, soket3 etc etc and never stop it is crap like Christian talk? really not understand ....

[Christian Ehrlicher]

@gfxx said in QTCP server ... possible run more than one?:

but these means every time need one istance need to choose the right from qvector

Why should you need one of these instances?

[jsulm]

@gfxx said in QTCP server ... possible run more than one?:

really not understand

And I don't understand the problem. Can you explain when you need these instances?

[gfxx]

@jsulm because data exchange is quite continuos and whitout any sort of regularity in format and type .... sometime file, sometime messages/string, sometime array/data structures .... if socket was interrupt need to have an advices and if need need to restart it 24/24 hour, 7/7 days ....

[Christian Ehrlicher]

@gfxx said in QTCP server ... possible run more than one?:

ecause data exchange is quite continuos and whitout any sort of regularity in format and type .... sometime file, sometime messages/string, sometime array/data structures .... if socket was interrupt need to have an advices and if need need to restart it 24/24 hour, 7/7 days ....

This does not answer any of our questions and does not even give a hint on what exact problems you have when you do a proper c++ encapsulation of the sockets in a worker thread... but maybe my c++ knowledge is to small.

[gfxx]

@Christian-Ehrlicher said in QTCP server ... possible run more than one?:

... but maybe my c++ knowledge is to small.

these is for make me laugh! thanks

so i try with worker thread and mySok class ... qabstractsocket::state:unconnected for kill worker ...

[Christian Ehrlicher]

@gfxx said in QTCP server ... possible run more than one?:

so i try with worker thread

Again: I never ever told you to use threads and will not do so anywhen in the future for such a task!

[gfxx]

@Christian-Ehrlicher said in QTCP server ... possible run more than one?:

Again: I never ever told you to use threads and will not do so anywhen in the future for such a task!

then I think I don't understand the term ... English is not my language ... you talk about worker thread .... but you mean the main thread on which the program works? .... because I understant only "worker.movetothread....." .... sorry ... so your solution is more istance of myClient class ..... so myclient1, myclient2..... because I know other pc and can choose them from ip adress and port number .... fixed istances for fixed ip adress&port number .... is what you means?

[SGaist]

Hi,

@Christian-Ehrlicher wrote: "worker object". It does not require any thread. It represents the class that will implement whatever needs to be done with your socket.

[gfxx]

@SGaist said in QTCP server ... possible run more than one?:

wrote: "worker object". It does not require any thread. It represents the class that will implement whatever needs to be done with your socket.

thanks...