[Qt-interest] Signal/Slot model is suitable for GUI applications but it isn't for console applications

[Eirik Ulvik]

I think it is safe to say that for inter-thread communication, queued
signals/slots are your only option while keeping processing in the
individual threads.
For signal/slot performance there is something in the docs:
http://doc.qt.nokia.com/4.6/templates.html in the chapter "Calling
Performance is Not Everything". However I would never emit a signal in a
tight for-loop or in compute intensive code. In my application I use
signals and slots for syncronisations between threads and such.

Regards,
Eirik

Den 23.08.2010 14:45, skrev Valeriy Portnyagin:
> hi all,
> 
> Could i say that Signal/Slot model is suitable for GUI applications but
> it isn't  for console applications?
> I am developing a console application with many threads. I am using the
> signals and slots between the threads.
> How much performance of my application will be worse at usage of
> Signal/Slot model?
> 
> regards,
> Valery Portnyagin.
> 
> 
> 
> _______________________________________________
> Qt-interest mailing list
> Qt-interest at trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-interest

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 551 bytes
Desc: OpenPGP digital signature
Url : http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20100823/87b11529/attachment.bin