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

[Valeriy Portnyagin]

compare with standard facilities for inter-thread communication - the 
direct call needed function (may be a virtual function) of the thread with 
some synchronization method like a mutex.

regards,
Valery Portnyagin.



From:
Sean Harmer <sean.harmer at maps-technology.com>
To:
qt-interest at trolltech.com
Date:
23.08.2010 16:57
Subject:
Re: [Qt-interest] Signal/Slot model is suitable for GUI applications but 
it isn't for console applications



On Monday 23 August 2010 13:45:10 Valeriy Portnyagin wrote:
> hi all,
> 
> Could i say that Signal/Slot model is suitable for GUI applications but 
it
> isn't  for console applications?

Not necessarily. We have several daemon applications written using Qt 
which 
utilise multiple threads.

> 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?

Compared to what? I assume you mean for inter-thread communication but 
what 
other method are you comparing it too?

Best way to tell is to benachmark the competing approaches.

Sean
_______________________________________________
Qt-interest mailing list
Qt-interest at trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-interest

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20100823/25fe5fa6/attachment.html