Re: Multithreading inside django

2006-12-03 Thread Wolfram Kriesing
Btw I found the problem ... details are here http://wolfram.kriesing.de/blog/index.php/2006/multithreading-with-mysqldb-and-weakrefs On 12/2/06, Wolfram Kriesing <[EMAIL PROTECTED]> wrote: > django/db/__init__.py contains > dispatcher.connect(connection.close, signal=signals.request_finished) >

Re: Multithreading inside django

2006-12-02 Thread Wolfram Kriesing
django/db/__init__.py contains dispatcher.connect(connection.close, signal=signals.request_finished) and that closes the connection and causes the exception below, the only thing i dont know is why the main thread doesnt closes it right away but instead lets the thread run a while and just the

Re: Multithreading inside django

2006-12-01 Thread Wolfram Kriesing
I think I found out that the connection is the same for both threads, I think that causes the problem. I will try some more but I am not sure if I am on the right path at all :-) On 11/30/06, Wolfram Kriesing <[EMAIL PROTECTED]> wrote: > From the frontend I trigger via AJAX a view that again

Multithreading inside django

2006-11-30 Thread Wolfram Kriesing
>From the frontend I trigger via AJAX a view that again starts a thread that does some import work, that might take quite a while. This enables the user to keep going and have the import run without interrupting him/her. Every once in a while an asynch call checks on the state of the import. And