--nextPart1214747316.AXza5iDVpt
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Sunday 29 June 2008, Sebastian Tr=FCg wrote:
> Apparently on Unix QLocalSocket uses QTcpSocket internally. This results =
in
> a big problem when I want to use it in a multithreaded environment as I
> cannot move the internal QTcpSocket to the new thread. Does anyone have an
> idea on how to solve this issue? On how to use QLocalSocket in
> multithreaded systems?

On the server or the client side?

On the client side you could use one QLocalSocket per thread.

On the server side you can use the incomingConnection(quintptr) template=20
method of QLocalServer and create the actual QLocalSocket in the target=20
thread's context. We do this in Akonadi, see=20
kdesupport/akonadi/server/src/akonadi.cpp and=20
kdesupport/akonadi/server/src/akonadiconnection.cpp

Cheers,
Kevin
=2D-=20
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring

--nextPart1214747316.AXza5iDVpt
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBIZ33JnKMhG6pzZJIRAm8FAJsGJVs1GhFrqN+xOuZgvOv5s5IJPgCfR74N
TGan2IvIN7u2UE0OmF/36ss=
=bNoC
-----END PGP SIGNATURE-----

--nextPart1214747316.AXza5iDVpt--