Interesting concurrency discussion on github

Howdy folks,

We should bring this discussion to the list:
https://gist.github.com/1233217

My last comment:
Threading and concurrency is interesting per se but I still don't see how it relates specifically to prevelance. In #liveDB the engine controls access to the model (prevalent system) allowing multiple readers and a single writer. The locking strategy is configurable and can be disabled. This is useful if the model itself is thread safe or if access is known to be single threaded. So far we haven't experienced any performance bottlenecks due to the single writer lock. One way the prevalence framework could assist is providing more granular locks, a feature easily implemented. We should go with transparent concurrency as far as possible.


--
Robert Friberg
Senior Architect, Devrex AB
0733-839080
Twitter: @robertfriberg
http://devrex.se/
http://se.linkedin.com/in/robertfriberg

[cid:[email protected]]

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2

_______________________________________________
To unsubscribe go to the end of this page: http://lists.sourceforge.net/lists/listinfo/prevayler-discussion
_______________________________________________
"Databases in Memoriam" -- http://www.prevayler.org