db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"<br>

%T Two\-Way Protocols for occam\-&pi;
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"<br>
%A  Adam T. Sampson
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"<br>
%E Peter H. Welch,  S. Stepney,  F.A.C Polack,  Frederick R. M. Barnes,  Alistair A. McEwan,  G. S. Stiles,  Jan F. Broenink,  Adam T. Sampson
%B Communicating Process Architectures 2008
%X In the occam\-&pi; programming language, the
   client\-server
communication pattern is generally
   implemented using a pair of
unidirectional channels. While
   each channel\[rs]s protocol can be
specified individually,
   no mechanism is yet provided to indicate the
relationship
   between the two protocols; it is therefore not possible
to
   statically check the safety of client\-server
   communications. This
paper proposes two\-way protocols for
   individual channels, which
would both define the structure
   of messages and allow the patterns
of communication between
   processes to be specified.We show how
conformance to
   two\-way protocols can be statically checked by
   the
occam\-&pi; compiler using Honda\[rs]s session types.
   These mechanisms
would considerably simplify the
   implementation of complex, dynamic
client\-server systems.