yes, threads share their status, but processes don't. If you need such a feature you probably want to give a look to an asyncrhonous queue. I wanted to provide redis backend to asyncjob for a long time, but I didn't have time to do so yet :/
On Mon, Mar 18, 2013 at 2:11 PM, Moritz Schlarb <[email protected]>wrote: > Hi there everyone, > > Is my assumption right, that when I use tgext.asyncjob and a > multithreaded server environment (like Paster with multiple threads), > each of the server instances will have it's own asyncjob worker thread > which don't share any information so different threads won't be able to > see statusses about jobs in other threads? > > Regards > > -- > Moritz Schlarb > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/turbogears?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/turbogears?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
