A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2005-October/057237.html below:

[Python-Dev] Pythonic concurrency

[Python-Dev] Pythonic concurrency [Python-Dev] Pythonic concurrencyPhillip J. Eby pje at telecommunity.com
Wed Oct 12 17:19:00 CEST 2005
At 02:35 AM 10/12/2005 +0000, Joshua Spoerri wrote:
>that stm paper isn't the end.
>
>there's a java implementation which seems to be exactly what we want:
>http://research.microsoft.com/~tharris/papers/2003-oopsla.pdf

There's already a Python implementation of what's described in the 
paper.  It's called ZODB.  :)  Just use the memory backend if you don't 
want the objects to persist.

Granted, if you want automatic retry you'll need to create a decorator that 
catches conflict errors.  But basically, ZODB implements a similar 
optimistic conflict management transaction algorithm to that described in 
the paper.  Certainly, it's the closest thing you can get in CPython 
without a complete redesign of the VM.

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4