db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"<br>
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"<br>
@InProceedings{Sufrin08,
  title =        "{C}ommunicating {S}cala {O}bjects",
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"<br>
  author=        "Sufrin,  Bernard",
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"<br>
  editor=        "Welch, Peter H. and Stepney,  S. and Polack,  F.A.C and Barnes,  Frederick R. M. and McEwan,  Alistair A. and Stiles,  G. S. and Broenink,  Jan F. and Sampson,  Adam T.",
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"<br>
  pages =        "35--54",
  booktitle=     "{C}ommunicating {P}rocess {A}rchitectures 2008",
  isbn=          "978-1-58603-907-3",
  year=          "2008",
  month=         "sep",
  abstract=      "In this paper we introduce the core features of CSO
     (Communicating
Scala Objects) \&amp;mdash; a notationally
     convenient embedding of the
essence of occam in a modern,
     generically typed, object-oriented
programming language that
     is compiled to Java Virtual Machine
(JVM) code. Initially
     inspired by an early release of JCSP,
CSO goes beyond JCSP
     expressively in some respects, including the
provision of a
     unitary extended rendezvous notation and
     appropriate
treatment of subtype variance in channels and
     ports. Similarities
with recent versions of JCSP include the
     treatment of channel ends
(we call them ports) as
     parameterized types. Ports and channels
may be transmitted
     on channels (including inter-JVM channels),
provided that an
     obvious design rule \&amp;mdash; the ownership rule
     \&amp;mdash; is
obeyed. Significant differences with recent
     versions of JCSP include
a treatment of network termination
     that is significantly simpler than
the
     \textlessq\textgreaterpoisoning\textless/q\textgreater
     approach (perhaps at the cost of reduced
     programming
convenience), and the provision of a family of
     type-parameterized
channel implementations with performance
     that obviates the need for
the special-purpose scalar-typed
     channel implementations provided by
JCSP. On standard
     benchmarks such as Commstime, CSO communication
performance
     is close to or better than that of JCSP and Scala's
Actors
     library."
}