aboutsummaryrefslogtreecommitdiffstats
path: root/src/declarative/debugger/qdeclarativeenginedebugservice_p.h
diff options
context:
space:
mode:
authorKai Koehne <kai.koehne@nokia.com>2011-08-24 13:51:07 +0200
committerQt by Nokia <qt-info@nokia.com>2011-11-22 13:45:27 +0100
commit43e20d57011bbddd3beec773f6a8efb1269a8ead (patch)
treee07e5b858582e6d689a188073a82249687be4c0e /src/declarative/debugger/qdeclarativeenginedebugservice_p.h
parent774eebf9978ac3bf68b124a9e88729cd21068433 (diff)
Debugger: Move server into it's own thread
So far the debugger infrastructure was running in the GUI thread, which required e.g. nested event loops to implement blocking behavior. The server and networking code are now running in their own thread, while the services are still running in the main thread. Because v8 isn't thread safe, we're adding two new JSEngines + isolates to qv8debugservice: One to decode JSON messages in the debugger thread, and one in the GUI thread. Change-Id: I746f5e203968f7bcc510fb66118c88ef0fd0cd14 Reviewed-by: Christiaan Janssen <christiaan.janssen@nokia.com>
Diffstat (limited to 'src/declarative/debugger/qdeclarativeenginedebugservice_p.h')
-rw-r--r--src/declarative/debugger/qdeclarativeenginedebugservice_p.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/declarative/debugger/qdeclarativeenginedebugservice_p.h b/src/declarative/debugger/qdeclarativeenginedebugservice_p.h
index 3674b83fe7..d3e5c79297 100644
--- a/src/declarative/debugger/qdeclarativeenginedebugservice_p.h
+++ b/src/declarative/debugger/qdeclarativeenginedebugservice_p.h
@@ -104,6 +104,7 @@ protected:
virtual void messageReceived(const QByteArray &);
private Q_SLOTS:
+ void processMessage(const QByteArray &msg);
void propertyChanged(int id, int objectId, const QMetaProperty &property, const QVariant &value);
private: