Paper Details

@InProceedings{SputhAllen05,
  title = "{JCSP}-{P}oison: {S}afe {T}ermination of {CSP} {P}rocess {N}etworks",
  author= "Sputh, Bernhard H.C. and Allen, Alastair R.",
  editor= "Broenink, Jan F. and Roebbers, Herman and Sunter, Johan P. E. and Welch, Peter H. and Wood, David C.",
  pages = "71--107",
  booktitle= "{C}ommunicating {P}rocess {A}rchitectures 2005",
  isbn= "978-1-58603-561-7",
  year= "2005",
  month= "sep",
  abstract= "This paper presents a novel technique for safe partial or
     complete process network termination. The idea is to have
     two types of termination messages / poison: LocalPoison and
     GlobalPoison. Injecting GlobalPoison into a process network
     results in a safe termination of the whole process network.
     In contrast, injected LocalPoison only terminates all
     processes until it is filtered out by Poison-Filtering
     Channels. This allows the creation of termination domains
     inside a process network. To make handling of a termination
     message easy, it is delivered as an exception and not as a
     normal message. The necessary Poisonable- and
     Poison-Filtering-Channels have been modelled in CSP and
     checked using FDR. A proof of concept implementation for
     Communicating Sequential Processes for Java (JCSP) has been
     developed and refined. Previously, JCSP offered no safe way
     to terminate the process network. When the user terminated
     the program, the Java Virtual Machine (JVM) simply stops all
     threads (processes), without giving the processes the chance
     to perform clean up operations. A similar technique is used
     to perform partial termination of process networks in JCSP,
     making it unsafe as well. The technique presented in this
     paper is not limited to JCSP, but can easily be ported to
     other CSP environments. Partial process network termination
     can be applied in the area of Software Defined Radio (SDR),
     because SDR systems need to be able to change their signal
     processing algorithms during runtime."
}

If you have any comments on this database, including inaccuracies, requests to remove or add information, or suggestions for improvement, the WoTUG web team are happy to hear of them. We will do our best to resolve problems to everyone's satisfaction.

Copyright for the papers presented in this database normally resides with the authors; please contact them directly for more information. Addresses are normally presented in the full paper.