Comments on: Not yet another … http://laurentszyster.be/blog/not-yet-another/ Python on Peers Sat, 04 Feb 2012 05:55:11 +0000 http://wordpress.org/?v=1.5.1.3 by: Lorenzo http://laurentszyster.be/blog/not-yet-another/#comment-183 Thu, 02 Feb 2006 13:57:07 +0000 http://laurentszyster.be/blog/not-yet-another/#comment-183 Why, have u guys missed crusader? ;-) http://www.movatis.com/crusader/ It's available through rpmfind (the download link on sourceforge doesn't work) here: http://rpmfind.net//linux/RPM/sourceforge/c/cr/crusader/crusader-0.7-2.noarch.html Why, have u guys missed crusader? ;-) http://www.movatis.com/crusader/

It’s available through rpmfind (the download link on sourceforge doesn’t work) here:
http://rpmfind.net//linux/RPM/sourceforge/c/cr/crusader/crusader-0.7-2.noarch.html

]]> by: Chris McDonough http://laurentszyster.be/blog/not-yet-another/#comment-182 Thu, 02 Feb 2006 13:55:19 +0000 http://laurentszyster.be/blog/not-yet-another/#comment-182 Medusa hits a sweet spot for me; it's small enough to understand entirely and very hackable. Things like "deferreds" are reasonably easy to add to Medusa (I did that recently by overriding "writable" and "refill_buffer" in an HTTP channel class). But in general, I do prefer having multiple threads around and just blocking when appropriate. It's decadent, I understand, but from a laziness perspective, it tends to beat the pants off of trying to return closures. If you're I/O bound and you need the raw speed, Medusa is great. But if you're compute-bound (as many content management systems are) it is often not worth turning your brain inside out to write everything in terms of a state machine. I don't think the convergence of Twisted and Zope has any significance to the death of threads. Zope, using either Medusa or Twisted, still maintains a thread pool for threads that do the actual work. Medusa hits a sweet spot for me; it’s small enough to understand entirely and very hackable. Things like “deferreds” are reasonably easy to add to Medusa (I did that recently by overriding “writable” and “refill_buffer” in an HTTP channel class). But in general, I do prefer having multiple threads around and just blocking when appropriate. It’s decadent, I understand, but from a laziness perspective, it tends to beat the pants off of trying to return closures. If you’re I/O bound and you need the raw speed, Medusa is great. But if you’re compute-bound (as many content management systems are) it is often not worth turning your brain inside out to write everything in terms of a state machine.

I don’t think the convergence of Twisted and Zope has any significance to the death of threads. Zope, using either Medusa or Twisted, still maintains a thread pool for threads that do the actual work.

]]>