In this paper, we propose the use of Versioned Boxes, which keep a history of values, as the basis for language-level memory transactions. Using Versioned Boxes to hold all the shared mutable state of a concurrent program, we can have lock-free concurrent programs which are much easier to develop and understand. Unlike previous work on software transactional memory, in our proposal read-only transactions never conflict with any other concurrent transaction. This may improve significantly the concurrency on applications which have longer transactions and a high read/write ratio. We discuss the use of speculative read-only transactions in such cases as a means to improve performance. Furthermore, we discuss how we can reduce transaction conflicts by developing concurrency-friendly objects-objects that are aware of and that cooperate with transactions. We propose two abstractions for this purpose: the per-transaction boxes and the restartable transactions. Finally, we discuss an extension to the versioned boxes model that generalizes the previous two abstractions.

International audienceBusiness Process Management is called agile when it is able to react quickly and adequately to internal and external events. Agile Business Process Management requires putting the life cycle of business processes on a new paradigm. It is advocated in this paper that social software allows us to satisfy the key requirements for enabling agile BPM by applying the four features of social software: weak ties, social production, egalitarianism and mutual service provision. Organizational and semantic integration and responsiveness (of the business processes engineering, execution and management activities) have been identified as the main requirements for implementing an agile BPM life cycle. Social software may be used in the BPM life cycle in several manners and using numerous approaches. This paper presents seven among them and then analyzes the 'support' effects between those approaches and the underlying social software features, and the three requirements for Agile BPM

No abstract