QTCP server ... possible run more than one?
-
@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??
@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 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...
@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 ....
bkt
-
@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 ....
@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 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 ....
@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 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?
@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 ....
bkt
-
@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 ....
@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.
Qt Online Installer direct download: https://download.qt.io/official_releases/online_installers/
Visit the Qt Academy at https://academy.qt.io/catalog -
@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.
@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 ...
bkt
-
@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 ...
@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!
Qt Online Installer direct download: https://download.qt.io/official_releases/online_installers/
Visit the Qt Academy at https://academy.qt.io/catalog -
@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!
@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?
-
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.
Interested in AI ? www.idiap.ch
Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct -
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.
