I've been looking into the kamaelia project http://kamaelia.sourceforge.net/Introduction.html which uses a different approach to multi tasking... essentially it uses inboxes and outboxes and the python yield mechanism for communication. They are using it for all sorts of interesting things!
My question is; how do you think this approach stacks up? I'd like to use it in an http streaming server for the purposes of a real time AJAX web application. But to be honest I would appreciate a 'real' developers point of view.. Thanks Ben -----Original Message----- From: Carl Cerecke [mailto:[EMAIL PROTECTED] Sent: Wednesday, 15 November 2006 12:14 p.m. To: [email protected] Subject: Re: Threads - was Re: ===>> 2007 Meetings <<=== On 15/11/06, Derek Smithies <[EMAIL PROTECTED]> wrote: > Which brings me back to the key idea: maybe when programmers say they hate > threads because of context switching issues and not needed, they are > really saying > > a)don't know about threads, have never been trained on them > b)hard to debug threads cause gdb etc don't handle threads well > c)there style of writing code is so messy that threads make it too > confusing. They could also be saying that there are alternatives to threads for concurrent programming that may be more suitable in many circumstances. That paper I referred to is online: http://www.eecs.berkeley.edu/Pubs/TechRpts/2006/EECS-2006-1.html The fact that the author is from one of the top three CS departments in North America (the other two being Stanford and MIT) lends his paper some extra weight, I think. I haven't looked for a rebuttal yet, though. Cheers, Carl.
