It is probably worth noting that since the Global Interpreter Lock is not released by the Metakit interface module this means that no other python threads will run pending the completion of the call. This is not so much thread-safe as thread-protected or serialized. The net effect, if your tasks are mostly I/O oriented, is that threading buys you nothing.
On Mon, 2005-05-09 at 07:41, Brian Kelley wrote: > My python metakit server shares a storage object between threads. In > fact, you have to do this if you are modifying contents between > threads. > > I have also used this successfully in a webware threaded web server > with no adverse effects. _____________________________________________ Metakit mailing list - [email protected] http://www.equi4.com/mailman/listinfo/metakit
