Paper Details

Using Java for Parallel Computing - JCSP versus CTJ

Authors: db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"
Schaller, Nan C., Hilderink, Gerald H., Welch, Peter H.

Paper URL: www.ce.utwente.nl/rtweb/publications/ 2000/030_R2000.pdf

Abstract:

Java provides support for concurrent and parallel programming throughthreads, monitors and its socket and Remote Method Invocation (RMI) classes.However, there have been many concerns expressed about the way in which thissupport is provided, e.g., [1][2], citing problems such as improper implementation ofmonitors and difficulty of programming with threads. Hoare’s CommunicatingSequential Processes (CSP) [3][4][5] model fully specifies thread synchronizationand is based on processes, compositions, and channel communication. It provides amathematical notation for describing patterns of communication using algebraicexpressions and contains formal proofs for analyzing, verifying and eliminatingundesirable conditions, such as race hazards, deadlocks, livelock, and starvation.Two independent research efforts provide a CSP based process-oriented designpattern for concurrency implemented in Java: Communicating Sequential Processesfor Java (JCSP) [6] and Communication Threads in Java (CTJ) [7]. In this paper, wecompare these two packages, looking at the philosophy behind their development,their similarities, their differences, their performance, and their use.

Proceedings:

Communicating Process Architectures 2000, db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"
Peter H. Welch, André W. P. Bakkers, 2000, pp 205 - 226 db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"
published by IOS Press, Amsterdam

This record in other formats: