Re: thread safe in python

Jack Diederich wrote:
> On Sat, May 07, 2005 at 12:39:28PM -0400, Eric S. Johansson wrote:
> 
>>just confirming.  googling indicates that using metakit with the python 
>>wrapper is thread safe.  still true with python 2.3.5?
>>
> 
> There haven't been any changes in python that would affect this.
> I just did a quick grep of the metakit source and I didn't see any
> calls to release python's GIL (global interpreter lock).  So calls
> out to metakit should be threadsafe just like calls into core python
> functions implemented in C are threadsafe (don't release the GIL).

thanks for confirming.  Now this raises the next level of question on 
thread safeness.  do I need to open a new storage object, view on every 
thread or share a single view between threads?

 From what I've read, it seems like storage objects should be shareable 
but is not clear at the level or any of the other things one can derive 
from a view.  My belief is that if each active row has only one writer, 
everything should be OK.

---eric


---
http://www.wired.com/wired/archive/13.03/view.html?pg=5

The result of the duopoly that currently defines "competition" is that
prices and service suck. We're the world's leader in Internet
technology - except that we're not.
_____________________________________________
Metakit mailing list  -  [email protected]
http://www.equi4.com/mailman/listinfo/metakit