I recently program with multi-threads (for about 1 year) under Linux only. I tried to follow your discussion. I will just tell my point of view, just to enlarge my understanding.
quote:Original post by Anonymous Poster
One thing i''ve noticed is the inherit latency of event based systems. Even though they usually are simpler and more efficient than a traditional polled or slot/signal approach, they suffer from higher latencies. For most applicaitons, I dont think this is a major issue, and in all cases an event based implementation can be reduced down into a more direct slot/signal implementaiton, with the tradeoff in compleixty and size.
Isn''t that latency that failed with the cpu battle between AMD and Intel ?
Latency is a real problem because your cpu do nothing, and may surely have better things to do.
quote:
Defintely using mutex for multithreaded data protection is a good idea, as that is their function. However using these object to handle flow of control distributedly and asychonrously, proably is not the best technique. I''ve found events to fill that role more efficiently, from my limited expereince.
-ddn
Yes, but I think again, seemly as above, that mutexes and condition waitings could do the same work with lower latency.
Flows depends on the data; and this may be an important thing for me: if you do events for handle flows, you must protect your data with something like mutex, otherwise, you may suffer from synchronization problem. Your flow may not be read at the same speed and frequency than its writting.
I surely may be wrong, this will permit me to understand why.
thank you.
