Abstract
Due to its speculative and also optimistic concurrencycontrol strategy, software transactional memory providesa scalable alternative to mutual exclusion. For the last fewyears, many implementations, which are basically variationsof the same design, have been released. Therefore is a consequentialstep to create a design pattern dealing with this issue.This paper proposes an approach for a software transactionalmemory design pattern called “Transactional Object”.
Full Text 
Sign-in/Register to access full text options
Sign-in/Register to access full text options 
Published version (
Free)
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
