Package org.jcsp.lang

Package org.jcsp.lang Description

Processes encapsulate both data and algorithms. Parallel processes interact either by synchronised communication along Channels (the cleanest and simplest way) or by synchronised access to shared objects. The latter synchronisation may be achieved through channel signals or by a range of other JCSP primitives (such as Barrier, AltingBarrier, Bucket or Crew).

Channels

Channels come in two varieties: those that carry Object references and those that carry ints. For completeness, JCSP should provide channels specific to all the Java primitive types. These could trivially be added but, so far, do not seem to be needed in practice.

Channels (from the Point of View of a Process)

Processes should drive their channels through channel interfaces: ChannelInput / ChannelOutput (for Object channels) and ChannelInputInt / ChannelOutputInt (for int channels).

Processes may passively wait for a number of events using Alternative. These events include channel inputs (AltingChannelInput / AltingChannelInputInt), channel accepts (AltingChannelAccept), alting barriers (AltingBarrier), timeouts (CSTimer) and skips (org.jcsp.lang.Skip). If more than one event is ready, an Alternative.select<I>arbitrary</I>, Alternative.priSelect<I>prioritised</I> or Alternative.select<I>fair</I> choice can be made between them. The super-interface for all these ALTable events is Guard.

Channels (from the Point of View of a Network)

Actual channels must be constructed by the org.jcsp.lang.Parallel network builder and passed to the processes needing them (usually via their constructors). Four varieties are available for Object channels: One2OneChannel, Any2OneChannel, One2AnyChannel and Any2AnyChannel. Similarly, four varieties are available for int channels: One2OneChannelInt, Any2OneChannelInt, One2AnyChannelInt and Any2AnyChannelInt. Please note that the last two in each set are not broadcasting channels - broadcasting has to be achieved by active processes (e.g. org.jcsp.plugNplay.Delta).

Note that the default semantics for all the above channels are zero-buffering and full synchronisation. This means that a writer to a channel will wait for a matching reader and vice-versa - whoever gets to the channel first will wait for its partner. Various forms of buffering can be introduced by splicing active buffer processes into these channels. However, because this is a common need, JCSP provides a range of plug-ins that can be used to create channels with the common varieties of buffering: org.jcsp.util.Buffer<I</code>blocking FIFO<code>>, org.jcsp.util.OverWriteOldestBuffer<I</code>overwriting (oldest) FIFO<code>>, org.jcsp.util.OverWritingBuffer<I</code>overwriting (latest) FIFO<code>> and org.jcsp.util.InfiniteBuffer<I</code>infinite FIFO<code>>. That set of plug-ins is for Object channels and comes from the org.jcsp.util package. A similar set for int channels is provided in org.jcsp.util.ints.

It is the network builder's responsibility to decide whether to use 1-1, any-1, 1-any or any-any channels and whether to incorporate buffers in them. The process designer is not concerned with these decisions - only with whether the channel is for input or output and what type of information it carries.

Call Channels

Call Channels provide a method interface for client-server communication between active processes, yet their semantics remain those of a synchronising zero-buffered channel. Without them, we would normally have to set up a pair of channels (giving bi-directional communication) and use a sequence of channel write(s) and read (at the client end) matched by a sequence of channel read(s) and write (at the server end).

The client process sees a server-specific method interface and invokes it in the normal way - however, the invocation will block until the server chooses to accept the call. The server sees the ChannelAccept interface - invoking an ChannelAccept.accept<TT>accept</TT> will block until the client makes a call.

The network builder constructs a server-specific actual call channel by sub-classing from one of One2OneCallChannel, Any2OneCallChannel, One2AnyCallChannel and Any2AnyCallChannel. Precise rules for making this extension are given in their documentation.