QTCP server ... possible run more than one?

gfxx

Problem become because use persisten connection from 4/5 client so instead to use multiple connection with qmapper ... i think to run more than one server with different port number ... so can be asyncronous and think not need to handle connection because connection is one to one .... but is possible?? It work .... data few there are not connection problem .... my idea was start server in these manner:

server1 = new QTcpServer(this);
connect(server1, SIGNAL(newConnection()), this, SLOT(newCon1()));
    if(!server->listen(QHostAddress("19x.16x.51.xxx"), xx051)
        qDebug() << "Server1 could not start";

server2 = new QTcpServer(this);
connect(server2, SIGNAL(newConnection()), this, SLOT(newCon2()));
    if(!server->listen(QHostAddress("19x.16x.51.xxx"), xx052)
        qDebug() << "Server 2could not start";

server3 = new QTcpServer(this);
connect(server3, SIGNAL(newConnection()), this, SLOT(newCon3()));
    if(!server->listen(QHostAddress("19x.16x.51.xxx"), xx053)
        qDebug() << "Server3 could not start";

server4 = new QTcpServer(this);
connect(server4, SIGNAL(newConnection()), this, SLOT(newCon4()));
    if(!server->listen(QHostAddress("19x.16x.51.xxx"), xx054)
        qDebug() << "Server4 could not start";

there are a so bad ideas?

Christian Ehrlicher

Why should this be needed? Handle each incoming connection in an own worker object and you're fine.

gfxx

@Christian-Ehrlicher so you suggest to convert all stuff for read single string, read file and write single string in qthread? So 3/4 or 10 qthread?

because client stay connected, and every 10sec send a string ... that string is a request of data or a command ... client can send 5/6 different command and based on command server can reply or send your own request .... i've not so mutch experiences with working thread (so my doubt) but seems a lot of things to do in working thread ....

Christian Ehrlicher

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

in qthread? So 3/4 or 10 qthread?

I never ever said anything about a thread here. I told you to apply your c++ knowledge about encapsulation and handle every connection in an separate object of the same class...

gfxx

@Christian-Ehrlicher ok thanks ... my misunderstand ....
but starting poit can be

client = server->nextPendingConnection();
chooseClient = client->peerAddress().toString();
QString client1 = "19x.16x.51.xx1";
QString client2 = "19x.16x.51.xx2";
QString client3 = "19x.16x.51.xx3";
QString client4 = "19x.16x.51.xx4";
if(chooseClient == client1){ some stuff1... /* how to assign actual connection to right socket1 with these ip?? */ }
else if(chooseClient == client2) { some stuff2../* how to assign actual connection to right socket2 with these ip?? */ } etc etc

after newconnection .....
I don't understand how I can distinguish one connection from another .... so let's assume that a client disconnects and then reconnects again .... the same call to newconnection will have to tell which client it is and it seems to me that in order to have a unique name getperradress is the only street ....

jsulm

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

I don't understand how I can distinguish one connection from another

For each connection you get a QTcpSocket. Don't know what the problem is. Can you explain why you need to know whether exact same client connects again? What is your use case?

"it seems to me that in order to have a unique name getperradress is the only street" - you can have more than one connection from same IP. A connection is defined by IP + port.

Christian Ehrlicher

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

after newconnection .....

No, this is crap.

Again: create a worker object for each connection and do your handling in there.

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 ...