On Feb 17, 9:33 pm, "C. Titus Brown" <[email protected]> wrote:
>
> How about just using a simple write lock around any sections that modify
> pygr.Data, or (even simpler) around any XML-RPC-exposed functions that
> modify pygr.Data?
I think a complete solution would need to lock around readers too to
ensure that no writing takes place while some other agent reads from
that resource. I heard it called MROW locking (multiple readers one
writer)
http://code.activestate.com/recipes/413393/
Might be an overkill though. Frankly due to the current implementation
of having pygr.Data a module, I wonder ... is it even possible to
reload pygr.Data while a reader is reading from it?
Istvan
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pygr-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/pygr-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
