<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>threads on chrismoos</title>
    <link>/tags/threads/</link>
    <description>Recent content in threads on chrismoos</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>&amp;copy; 2020 Chris Moos</copyright>
    <lastBuildDate>Wed, 04 Mar 2009 00:03:53 +0000</lastBuildDate><atom:link href="/tags/threads/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Pylons Worker Threads</title>
      <link>/2009/03/04/pylons-worker-threads/</link>
      <pubDate>Wed, 04 Mar 2009 00:03:53 +0000</pubDate>
      
      <guid>/2009/03/04/pylons-worker-threads/</guid>
      <description>I was reading a thread over at pylons-discuss about worker threads in pylons. Worker threads are useful if you need to execute a long running task, but want to return to the user immediately. You could run a new thread per request, but if you have many requests, it is probably better to queue things up.
To do this, you start a thread and use python&amp;rsquo;s Queue for managing the tasks.</description>
    </item>
    
  </channel>
</rss>
