As Mr. Kale so eloquently puts it (and of course 100% correct):
- If you think you need multi-threading, you're wrong
- If your specification says "you need threading", see Rule 1
- (For advanced users only) If you think you need multi-threading, you're probably wrong.
Similar posts to check out:
- June 16, 2011 -- Occasionally Connected Architecture (0)
When implementing an occasionally connected architecture for a solution, there are three fundamental requirements: Part of the overall solution, some smart client is deployed and installed on the desktop and a web only approach is not possible. The main rational being that a smart client can work in a disconnected mode which of course with a web application is not possible. Underlying infrastructure needs to be in place to support this. Infrastructure is not specifically networks and ser... - December 29, 2010 -- C++ Message queuing options? (1)
I am thinking of implementing a queue in one of the projects I am working on right now (sorry cannot go into more details until it gets published - hopefully in a few months). Anywyas, this is in C++ which needs to run on Ubuntu and my queueing experience (with C++ or otherwise) is only with MSMQ which is brilliant, but does not help me here as that run only on Windows. I also cannot use something like STL Queue as this will need to run across a number of machines and trying to sync between them... - November 6, 2010 -- MOOS (0)
I don't think many people have heard of MOOS (which stands of Mission Oriented Operating Suite); I have been working with it for the past few months as part of my dissertation. And I must admit, the more I play with it, the more impressed I am. It is quite simple and yet powerful.
Whilst MOOS's roots are in robotics (MRG) and embedded systems, I wonder if I can extend it to use it some of the grid computing scenarios. Maybe implement a pMapReduce or pHadoop? Or perhaps a .NET implementation. ...
Tags: .architecture
