Andreas Masur
On Dec 17, 2008, at 10:09 AM, QuitePlace wrote:
Another look at this question is - should one program the inter- process/inter- thread communication first and worry about multi-core later? Or something should be planned at the development stage?
As with other areas such as exception handling etc., I would advise you to take multi-core technology into account at design time. Programing efficiently for more than one core is certainly not as easy as making cookies and thus if you don't plan up front you are likely to lose efficiency later on. Especially in your example about interprocess/interthread communications.
Ciao, Andreas
This is exactly what worries me. Should that planning be done "outside" of boost framework? For example, if I am using features provided by ::interconnect library - how am I suppose to take multi-core technology into account if, say, "shared memory" already locks me into a solution where I don't have much control on anything multi-core and where "multi-core" is not even present as a concept? Your comments are very much appreciated