Comments on: Twisted concurrency with Bruce Eckel. http://jessenoller.com/2008/05/03/twisted-concurrency-with-bruce-e/ python, programming and other things Tue, 06 Jan 2009 10:45:03 +0000 http://wordpress.org/?v=2.7 hourly 1 By: Orestis Markou http://jessenoller.com/2008/05/03/twisted-concurrency-with-bruce-e/comment-page-1/#comment-62215 Orestis Markou Sun, 04 May 2008 17:49:14 +0000 http://jessenoller.com/2008/05/03/twisted-concurrency-with-bruce-e/#comment-62215 I spent the past few hours trying to make Bruce's example a bit more manageable - I aim to write a short blog post describing my little helper module.<br><br>The thing I don't like in the twisted async approach is the "spaghetti execution" model. When reading code, the pattern "search for callRemote, hunt for the callbacks" is very tiring. I'm aiming to put all this information to a big event dictionary, so instead of attaching callbacks, you listen for event (which delegate to the defined callbacks). <br><br>Anyway, more soon (hopefully) here: <a href="http://orestis.gr" rel="nofollow">http://orestis.gr</a> I spent the past few hours trying to make Bruce's example a bit more manageable - I aim to write a short blog post describing my little helper module.

The thing I don't like in the twisted async approach is the “spaghetti execution” model. When reading code, the pattern “search for callRemote, hunt for the callbacks” is very tiring. I'm aiming to put all this information to a big event dictionary, so instead of attaching callbacks, you listen for event (which delegate to the defined callbacks).

Anyway, more soon (hopefully) here: http://orestis.gr

]]> By: jnoller http://jessenoller.com/2008/05/03/twisted-concurrency-with-bruce-e/comment-page-1/#comment-62214 jnoller Sun, 04 May 2008 13:37:46 +0000 http://jessenoller.com/2008/05/03/twisted-concurrency-with-bruce-e/#comment-62214 Twisted does have that benefit - it also has the benefit of hiding the network magic from you. In both the twisted and processing case, you are going to need to have the server exec something on the clients and clients running a listener for the object being passed to them.<br><br>Processing has the concept of managers/listeners that do the same thing, the one big draw twisted does have is the reactor async model which allowed Bruce in this case, to keep the UI server running/listening for events while the solvers were dispatched. Twisted does have that benefit - it also has the benefit of hiding the network magic from you. In both the twisted and processing case, you are going to need to have the server exec something on the clients and clients running a listener for the object being passed to them.

Processing has the concept of managers/listeners that do the same thing, the one big draw twisted does have is the reactor async model which allowed Bruce in this case, to keep the UI server running/listening for events while the solvers were dispatched.

]]> By: Orestis Markou http://jessenoller.com/2008/05/03/twisted-concurrency-with-bruce-e/comment-page-1/#comment-62213 Orestis Markou Sun, 04 May 2008 12:57:00 +0000 http://jessenoller.com/2008/05/03/twisted-concurrency-with-bruce-e/#comment-62213 Can you do grid-like (multiple computers) coordination with processing? It seems like twisted offers a very elegant and simple way to create small daemons that are coordinated from a server. Can you do grid-like (multiple computers) coordination with processing? It seems like twisted offers a very elegant and simple way to create small daemons that are coordinated from a server.

]]>