| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Change-Id: I51934b0de77b1062153f5f60be44d4bcf4be5ee5
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
| |
|
|
|
|
|
|
|
|
| |
Due do the fact that we can have several threads call to
RemoteClient::instance() at the same time, some objects might
get a not fully initialized object back. Most notable members
of private class where initialized differently or not at all.
Change-Id: I80fc4ad59583e3784c0e9f002e23d3df91f127b2
Reviewed-by: Christian Stenger <christian.stenger@digia.com>
|
| |
|
|
|
|
|
|
|
|
| |
The keep alive thread does try to delete the socket it gets
from the connect method, but since the socket was created in
a different thread and we will hit the:
"Socket notifiers cannot be disabled from another thread" warning.
Change-Id: Ibafcd67f8cdb51b365c3ef230f1ebd447bdd306a
Reviewed-by: Niels Weber <niels.weber@digia.com>
|
|
|
Still based on what we had already, though more separated.
Change-Id: I4cce298003a4ffc2ebcec01fea1a07adfbfdf990
Reviewed-by: Tim Jenssen <tim.jenssen@digia.com>
Reviewed-by: Niels Weber <niels.weber@digia.com>
|
