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{SchweigleBarnes03,
  title =        "{F}lexible, {T}ransparent and {D}ynamic occam {N}etworking {W}ith {KR}o{C}.net",
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"<br>
  author=        "Schweigler,  Mario and Barnes,  Frederick R. M. and Welch, Peter H.",
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"<br>
  editor=        "Broenink,  Jan F. and Hilderink,  Gerald H.",
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"<br>
  pages =        "199--224",
  booktitle=     "{C}ommunicating {P}rocess {A}rchitectures 2003",
  isbn=          "1 58603 381 6",
  year=          "2003",
  month=         "sep",
  abstract=      "KRoC.net is an extension to KRoC supporting the distribution
     of occamchannels over networks, including the internet.
     Starting in 2001, the development ofKRoC.net has gone
     through a number of stages, each one making the system
     moreflexible, transparent and dynamic. It now enables the
     occam programmer to set upand close network channels
     dynamically. Configuration has been simplified. All
     occamPROTOCOLs can now be sent over network channels,
     without need for conversion.Many of the new dynamic features
     in occam have been used to improve KRoC.net.Many of the
     concepts in KRoC.net are similar to those in the JCSP
     Network Edition(JCSP.net), KRoC.net’s counterpart in the
     JCSP world. This paper will give an overviewover KRoC.net,
     its usage, its design and implementation, and its future. It
     willalso provide some benchmarks and discuss how the new
     occam features are beingused in the latest KRoC.net version."
}