Talks and Poster Presentations (with Proceedings-Entry):
"Client and Server Synchronization Expressed in Types";
Talk: Synchronization and Concurrency in Object-Oriented Languages (SCOOL), Workshop at OOPSLA 2005,
San Diego, California, USA;
2005-10-16; in: "Synchronization and Concurrency in Object-Oriented Languages (SCOOL)",
Synchronization based on semaphores, monitors, or atomic actions is in general not visible through object types. Often we use unnecessary or even conflicting synchronization in clients and servers because of missing information. Process types -- a kind of behavioral types -- solve this problem so far only partially: Types specify synchronization required from clients, but they hide the servers' synchronization. In this paper we propose a solution based on dynamic token management (in addition to static token management already existing in process types). This approach extends conventional object types in a straightforward way, supports subtyping under consideration of synchronization, ensures race-free programs, and still does not expose implementation details to clients.
Online library catalogue of the TU Vienna:
Electronic version of the publication:
Created from the Publication Database of the Vienna University of Technology.