[Development] QTcpSocket, QLocalSocket, common-use-model?

[Thiago Macieira]

On quarta-feira, 10 de outubro de 2012 11.03.21, Kevin Krammer wrote:
> Not related to performance, but often the main reason to use techniques
> such  as QLocalSocket is better access control.
> Any process (running as any user) on the machine can attempt a connect to a 
> TCP socket on the loopbar device, while e.g. Unix domain sockets can be
> created such that only processes of the same user can attempt connections.

True. What's more, you can use SO_PEERCRED and file-descriptor passing on Unix 
sockets, but you can't on TCP sockets.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20121010/59261d22/attachment.sig>