Last updated on Monday, October 06, 2025
@inproceedings{TichelaarSAC2000,
author = {Sander Tichelaar and Juan Carlos Cruz and
Serge Demeyer},
booktitle = {Proceedings {SAC}'00 ({ACM} Symposium on Applied
Computing)},
editor = {Janice Carroll and Ernesto Damiani and Hisham Haddad and
Dave Oppenheim},
month = mar,
note = {Acceptance ratio: 194/457 = 42\%},
pages = {270-277},
publisher = {ACM},
title = {Design Guidelines for Coordination Components},
year = {2000},
abstract = {The distributed nature of a typical web application
combined with the rapid evolution of underlying
platforms demands for a plug-in component
architecture. Nevertheless, code for controlling
distributed activities is usually spread over
multiple subsystems, which makes it hard to
dynamically reconfigure coordination services. This
paper investigates coordination components as a way
to encapsulate the coordination of a distributed
system into a separate, pluggable entity. In an
object-oriented context we introduce two design
guidelines (namely, "turn contracts into objects" and
"turn configuration into a factory object") that help
developers to separate coordination from computation
and to develop reusable and flexible solutions for
coordination in distributed systems.},
annote = {internationalconference},
}