Make the underlying transport mechanism of the webchannel pluggable.

This enables us to optionally use navigator.qt instead of a WebSocket,
which is nicer setup-wise and is also slightly faster:

navigator.qt:
284.0 msecs per iteration (total: 2,840, iterations: 10)
WebSocket:
295.8 msecs per iteration (total: 2,959, iterations: 10)

The baseline is ca. 203 msecs, which would mean a performance boost
of ca. 12.7%.

Furthermore, this sets the fundation to eventually add a WebEngine
transport mechanism. The WebViewTransport should also be removed and
instead the WebView itself should directly implement the
WebChannelTransportInterface.

Change-Id: I368bb27e38ffa2f17ffeb7f5ae695690f6f5ad21
Reviewed-by: Simon Hausmann <simon.hausmann@digia.com>

1 files changed, 5 insertions, 2 deletions

diff --git a/src/webchannel/qwebchannel_p.h b/src/webchannel/qwebchannel_p.h
index 63f5a0a..954134e 100644
--- a/src/webchannel/qwebchannel_p.h
+++ b/src/webchannel/qwebchannel_p.h
@@ -43,16 +43,19 @@
 #define QWEBCHANNEL_P_H
 
 #include "qwebchannelglobal.h"
+#include "qwebchanneltransportinterface.h"
+
+#include <QVector>
 
 QT_BEGIN_NAMESPACE
 
 class QJsonValue;
-class QWebChannelSocket;
+class QWebChannelTransportInterface;
 class QMetaObjectPublisher;
 
 struct Q_WEBCHANNEL_EXPORT QWebChannelPrivate
 {
-    QWebChannelSocket *socket;
+    QVector<QWebChannelTransportInterface*> transports;
     QMetaObjectPublisher *publisher;
 
     void sendJSONMessage(const QJsonValue &id, const QJsonValue &data, bool response) const;