kazu2012 / persevere-framework

Automatically exported from code.google.com/p/persevere-framework
0 stars 0 forks source link

Full ACID Compliance #30

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Currently transactions are not fully atomic, and queries do not utilize
information from modifications within a transaction. I intend to provide
software transactional memory management style code restarting and
time-stamp based concurrency to provide full consistent ACID compliance and
provide simple concurrency semantics for JavaScript code.

Original issue reported on code.google.com by kris...@gmail.com on 1 Dec 2008 at 3:39

GoogleCodeExporter commented 8 years ago

Original comment by kris...@gmail.com on 30 Apr 2009 at 3:35

GoogleCodeExporter commented 8 years ago
This issue is a showstopper for me testdriving/using Persevere; please tell us 
that
it doesn't have to be a showstopper in real life web apps; by pointing us to
(existing) docs/examples that deal with this missing ACID compliancy; and show 
us why
and how it is nonetheless possible to bet our fortune on Persevere with faith 
... 

Original comment by k...@kaitischler.de on 2 Jul 2009 at 11:48