qDebug() << "Client connected:" << pSocket->peerName() << pSocket->origin();
- connect(pSocket, &QWebSocket::textMessageReceived, this, &SslEchoServer::processMessage);
+ connect(pSocket, &QWebSocket::textMessageReceived, this, &SslEchoServer::processTextMessage);
connect(pSocket, &QWebSocket::binaryMessageReceived,
this, &SslEchoServer::processBinaryMessage);
connect(pSocket, &QWebSocket::disconnected, this, &SslEchoServer::socketDisconnected);
}
//! [onNewConnection]
-//! [processMessage]
-void SslEchoServer::processMessage(QString message)
+//! [processTextMessage]
+void SslEchoServer::processTextMessage(QString message)
{
QWebSocket *pClient = qobject_cast<QWebSocket *>(sender());
if (pClient)
Q_UNUSED(bytesWritten);
}
}
-//! [processMessage]
+//! [processTextMessage]
//! [processBinaryMessage]
void SslEchoServer::processBinaryMessage(QByteArray message)
private Q_SLOTS:
void onNewConnection();
- void processMessage(QString message);
+ void processTextMessage(QString message);
void processBinaryMessage(QByteArray message);
void socketDisconnected();
The client socket is remembered in a list, in case we would like to use it later
(in this example, nothing is done with it).
- \snippet echoserver/echoserver.cpp processMessage
- Whenever `processMessage()` is triggered, we retrieve the sender, and if valid, send back the
+ \snippet echoserver/echoserver.cpp processTextMessage
+ Whenever `processTextMessage()` is triggered, we retrieve the sender, and if valid, send back the
original message (`send()`).
The same is done with binary messages.
\snippet echoserver/echoserver.cpp processBinaryMessage