tgext.asyncjob and multithreaded Server

[Moritz Schlarb]

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

[Alessandro Molina]

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 :/

--
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 turbogears+...@googlegroups.com.
To post to this group, send email to turbo...@googlegroups.com.
Visit this group at http://groups.google.com/group/turbogears?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Craig Small]

On Mon, Mar 18, 2013 at 02:11:13PM +0100, Moritz Schlarb wrote:
> which don't share any information so different threads won't be able to
> see statusses about jobs in other threads?

I'm using zeroMQ for my inter-thread communications for my backend stuff
(there's a fair bit of that going on). But yes, you need something do do
that sort of communication.

- Craig
--
Craig Small VK2XLZ http://enc.com.au/ csmall at : enc.com.au
Debian GNU/Linux http://www.debian.org/ csmall at : debian.org
GPG fingerprint: 5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5

[Alessandro Molina]

Pointing out that there is now a development version of tgext.asyncjob that support sharing task status on Redis, so that it can be used between multiple processes.

Refer to https://groups.google.com/d/msg/turbogears-trunk/JF5KpXPRR2o/0SASJOw-vhoJ announce for more informations.

It will probably be released next week.