QWebSocket and QUrl have so many functions to check if they're valid or not or what's currently going on - you should use them.

I think that I found my answer https://wiki.qt.io/Qt_6.0.0_Modules Not supported. [image: d9040d3b-d348-4864-abd7-275b2f07c331.png] Thanks for help. I guess I will have to try to rollback. I wanted to write a small simple app for (for now) my own use, but the functionalities seem to be pretty restricted on Qt 6.0 then...

Hi, There's a pretty interesting Ars Technica article about netcode in fighting games. Worth a read.

I solved ! The author of the libwebsockets library suggested me to initialize the engine with a default subprotocol if the client did not define it. And it worked ! Thanks!

Hi @Geeva, @Geeva said in JSON with multi tasking: @JKSH Thanks for solving basic confusion. I have one more doubt also. Here, I have attached program for verification. I hope you can provide a proper solution You're welcome. I'm happy to teach you basics. However, verifying your program is too difficult to do on a forum. You need to do 2 things: Take C++ lessons Practice writing and debugging simple programs for your hardware

@Geeva The easies way is to move your task into its own function that expects q QList<QString> as an argument: void myClass::myFunction(QList<QString> startvalue){ //do stuff eg: qDebug() << "Value Received from server :" << startvalue; QStringList first = startvalue.split("|"); int firstSize = first.size(); qDebug() << "size :" << firstSize; if(firstSize == 5){ first1 = first[2]; first2 = first[3]; }..........(continue) } then you call that function for each and every item in your QList<QList<QString>> QList<QList<QString> > myList for(QList<QString> ls : myList){ myFunction(ls); }

Where are you OpenSSL .dll located ?

Thanks for the link ! I haven't yet been able to get it working. But I suspect I should probably be using a Loader with a Canvas component, instead of a simple Image element. I'll test it out and let you know. If anyone has a working code, don't hesitate to share ^^ I'm sure it would be a great example to include in the docs. Daniel

@kshegunov ok now I understand! Thanks!

@mistralegna AFAIK, You can set bool QAbstractSocket::isValid() const on the given address provided. you can also get error signal from the websocket, if it is not valid address. void QAbstractSocket::error(QAbstractSocket::SocketError socketError). check here . But , the isvlaid() is not very efficient like in your case WS:// instead of WSS://. Because to my knowledge isValid() says true to any address , if it is inform of address/standard way of address. In your cases, I prefer to use Regular Expression before connection to socket.

I didn't. But also it didn't fixed the error. The QT client can connect to the server with wss. The Webclient can't connect to the server with wss. But an echo test to "wss://echo.websocket.org" is successfully, so the browser is okay. The question is, what's the difference between Qt secure websocket and the other solutions? Is it may some different SSL/TSL config? I'm using QSsl::TlsV1SslV3

OK guys i can confirm this is a bug in the Qt5.3 (linux version at least); as the exact same code on Qt5.5 on windows produces the followin output : Message received: "Hello, world!" Close code: 1002 Was already reported btw : [https://bugreports.qt.io/browse/QTBUG-42982](link url)

Self-signed certificate are always the more complicated to manage (i.e. nobody trust them since no valid CA validated them) Sorry, I'm don't remember of such a howto... No, there won't be another release of Qt 5.3. The next release is 5.6.0 the first LTS of Qt 5.

You're welcome ! Since you have what you need now, please mark the thread as solved using the "Topic Tool" button so that other forum members may know a solution has been found :) Also, while browsing the forum, consider up-voting answers that helped you. That will make them easier to find for other forum users :)

@TeunGri173 I did a test against http://www.websocket.org/echo.html with QWebView in my application. This test is working correctly. So there is someting with the QWebSocketServer I use. The only I do is: ws = new QWebSocketServer("", QWebSocketServer::NonSecureMode, this); ws->listen( QHostAddress::Any, 13031); And of course connect to the newConnection() signal. resume test results: Backend Frontend Result websocket.org QWebView OK websocket.org FireFox OK websocket.org Chrome OK QWebSocketServer QWebView FAIL QWebSocketServer FireFox OK QWebSocketServer Chrome OK Only the combination QWebSocketServer / QWebView failed. Any hints wat to configure in QWebSocketServer ? Or could it possibly be a bug ? Thanks in advance for your info.

What version of Qt are you using ? And how did you install it ?

In that case the QtWebSocket module is indeed a good starting point

@JKSH Thank you. Now WebSockets work :)