Re: Interesting concurrency discussion on github

My point is to play with a 'transaction stream/lazy evaluation' design
instead of a "static/shared variables' one..

Since prevayler (or any other prevalence implementation) already keep track
of objects transactions history, how can we use this in order to implement
rollback, avoid excessive locking and help users to design clean, fast and
thread-safe code.

I can be completely wrong.. :)

Anyone here knows Deuce? Java STM implementation:

http://www.deucestm.org/Home

this doc is cool
https://docs.google.com/present/view?id=ddmbgvw3_685gbtz97gh



2011/9/25 Robert Friberg <[email protected]>

> 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****
>
> ** **
>
> [image: Description: Devrex logotype]****
>
> ** **
>
>
> ------------------------------------------------------------------------------
> 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
>
>

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1

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