I would suggest a three phase model for transactions operating on shared resource: 1.) prepare phase: multiple readers/one writer have access to the resource 2.) modification phase: only one writer has access and can can modify the resource 3.) commit/rollback phase: write publishes its local modifications and releases the execlusive lock With this pattern you cold support queries and transactions in parrallel (at least for phase 1 and 3). Oliver vicente.botet wrote:
Hi Stefan, Bob,
I've created in the sandbox the transaction directory (http://svn.boost.org/svn/boost/sandbox/transaction/) so we can share our work. I've created also a wiki page (http://svn.boost.org/trac/boost/wiki/BoostTransaction) on which we can compile the result of our discussions, requirements for the library, design, ...
If you don't have right access to the Boost wiki pages, please request them throught this ML.
Of course, anyone is welcome to participate, or comment on this wiki.
HTH, _____________________ Vicente Juan Botet Escribá _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost