Paper Details

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"
@InProceedings{LarsenVinter12,
  title = "{E}xception {H}andling and {C}heckpointing in {CSP}",
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"
  author= "Larsen, Mads Ohm and Vinter, Brian",
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"
  editor= "Welch, Peter H. and Barnes, Frederick R. M. and Chalmers, Kevin and Pedersen, Jan Bækgaard and Sampson, Adam T.",
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"
  pages = "201--212",
  booktitle= "{C}ommunicating {P}rocess {A}rchitectures 2012",
  isbn= "978-0-9565409-5-9",
  year= "2012",
  month= "aug",
  abstract= "This paper describes work in progress. It presents a new way
     of looking at some of the basics of CSP. The primary
     contributions is exception handling and checkpointing of
     processes and the ability to roll back to a known
     checkpoint. Channels are discussed as communication
     events which is monitored by a supervisor process. The
     supervisor process is also used to formalise poison and
     retire events. Exception handling and checkpointing are
     used as means of recovering from an catastrophe.
     The supervisor process is central to checkpointing and
     recovery as well. Three different kind of exception handling
     is discussed: fail-stop, retire-like fail-stop, and check
     pointing. Fail-stop works like poison, and retire-like
     fail-stop works like retire. Checkpointing works by telling
     the supervisor process to roll back both participants in
     a communication event, to a state immediately after their
     last successful communication. Only fail-stop exceptions
     have been implemented in PyCSP to this point."
}

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.