2005
DOI: 10.1007/11424529_17
|View full text |Cite
|
Sign up to set email alerts
|

A Component-Oriented Model for the Design of Safe Multi-threaded Applications

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2008
2008
2009
2009

Publication Types

Select...
1
1

Relationship

0
2

Authors

Journals

citations
Cited by 2 publications
(3 citation statements)
references
References 10 publications
0
3
0
Order By: Relevance
“…However, the operations might implement complex collaborations with other controllers to acquire a set of resources while avoiding deadlock. Approaches that employ this pattern include SyncGen, which generates them from declarative region invariants [10], the system of Betin-Can and Bultan, which generates them from action-language specifications [6], and our own Szumo system, which generates them from declarative synchronization contracts [25,5].…”
Section: Approaches To Separation and Automatic Programming Of Synchrmentioning
confidence: 99%
See 2 more Smart Citations
“…However, the operations might implement complex collaborations with other controllers to acquire a set of resources while avoiding deadlock. Approaches that employ this pattern include SyncGen, which generates them from declarative region invariants [10], the system of Betin-Can and Bultan, which generates them from action-language specifications [6], and our own Szumo system, which generates them from declarative synchronization contracts [25,5].…”
Section: Approaches To Separation and Automatic Programming Of Synchrmentioning
confidence: 99%
“…We previously integrated Szumo into an extension of the Eiffel language [3,25] and, more recently, implemented it in C++ as a framework [11]. A case study in evolving and maintaining a multithreaded web server demonstrates how the use of synchronization contracts supports maintenance activities [5]. The work described in the current paper shows how synchronization contracts can be used to make container-level synchronization policies more flexible with regard to how, when, and how many objects are locked during the servicing of a message.…”
Section: Synchronization Contractsmentioning
confidence: 99%
See 1 more Smart Citation