This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Data concurrency is a complex subject and usually it is achieved through specific database technologies and transaction isolation levels. However there are other vendor specific strategies. WebLogic for example has four concurrency strategies:
The default is the database concurrency strategy, which will delegate the responsibility of data locking to the underlying database system. The optimistic strategy enforces concurrency using the classic client/server approach of ensuring that the data have not been changed by other clients during the transaction. This of course works only with CMP and for each update the container will issue a query like this:
I think, therefore I exist -- Rene Descartes
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com