ZStorm tied too closely to threaded transaction managers
Bug #279945 reported by
Gary Poster
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Storm |
New
|
Undecided
|
Unassigned |
Bug Description
In zstorm's synchronizer, this condition concerns me:
if store and trans is transaction.get():
Why do we need to verify that the trans is the same as trans.get()? This seems unnecessary to me, and even problematic since it potentially keeps the data manager away from the transaction manager.
In general, I think ZStorm should support explicit (non threaded) transaction managers. They are used and come in handy.
To post a comment you must log in.
First of all, the zstorm code is explicitly designed to manage per-thread stores, so working with the standard threaded transaction manager seems appropriate. That said, some bits of code could be reused with other transaction managers (e.g. the DataManager implementation).
What sort of API are you looking for, and what sort of problems are you trying to solve?