[Interest] QNetwork problem in threaded application (repost from development).

[Thiago Macieira]

On segunda-feira, 9 de setembro de 2013 21:46:56, Benjamin Zeller wrote:
> Is it maybe possible that due to high load the ThreadChange Event gets
> lost (or is delivered too late)? The socket descriptor is then never 
> disabled and reenabled , which means the thread affinity would be wrong.

The ThreadChange event is sent synchronously with sendEvent, which causes 
QSocketNotifier to synchronously unregister itself. It can't get lost due to 
high load.

But like I asked you on IRC: it may get lost if an event filter discards it.

-- 
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/interest/attachments/20130909/21249ae7/attachment.sig>