Cooperative Task Management without Manual Stack Management or, Event-driven Programming is Not the Opposite of Threaded Programming

Cooperative Task Management without Manual Stack Management or, Event-driven Programming is Not the Opposite of Threaded Programming (2002)

Cached

Download Links

Other Repositories/Bibliography

DBLP

by Atul Adya , Jon Howell , Marvin Theimer , William J. Bolosky , John R. Douceur

Venue:	In Proceedings of the 2002 Usenix ATC
Citations:	85 - 0 self

Versions

Version History

Metadata Version 3

User correction supplied by SystemCorrections

Datum	Value	Source
TITLE	Cooperative Task Management without Manual Stack Management or, Event-driven Programming is Not the Opposite of Threaded Programming	user correction - Legacy Corrections
AUTHOR NAME	Atul Adya	SVM HeaderParse 0.1
AUTHOR AFFIL	Microsoft Research; 1 Microsoft Way	SVM HeaderParse 0.2
AUTHOR ADDR	Redmond, Washington 98052	SVM HeaderParse 0.1
AUTHOR NAME	Jon Howell	SVM HeaderParse 0.1
AUTHOR AFFIL	{adya,	SVM HeaderParse 0.2
AUTHOR NAME	Marvin Theimer	SVM HeaderParse 0.1
AUTHOR AFFIL	{adya,	SVM HeaderParse 0.2
AUTHOR NAME	William J. Bolosky	SVM HeaderParse 0.1
AUTHOR AFFIL	{adya,	SVM HeaderParse 0.2
AUTHOR NAME	John R. Douceur	SVM HeaderParse 0.1
AUTHOR AFFIL	{adya,	SVM HeaderParse 0.2
ABSTRACT	Cooperative task management can provide program architects with ease of reasoning about concurrency issues. This property is often espoused by those who recommend "event-driven" programming over "multithreaded " programming. Those terms conflate several issues. In this paper, we clarify the issues, and show how one can get the best of both worlds: reason more simply about concurrency in the way "event-driven" advocates recommend, while preserving the readability and maintainability of code associated with "multithreaded" programming. We identify the source of confusion about the two programming styles as a conflation of two concepts: task management and stack management. Those two concerns define a two-axis space in which "multithreaded" and "event-driven" programming are diagonally opposite; there is a third "sweet spot" in the space that combines the advantages of both programming styles. We point out pitfalls in both alternative forms of stack management, manual and automatic, and we supply techniques that mitigate the danger in the automatic case. Finally, we exhibit adaptors that enable automatic stack management code and manual stack management code to interoperate in the same code base.	user correction - Legacy Corrections
YEAR	2002	INFERENCE
VENUE	In Proceedings of the 2002 Usenix ATC	INFERENCE
VENUE TYPE	CONFERENCE	INFERENCE
CITATIONS	13 found	ParsCit 1.0