Package org.jcsp.net.cns

This package contains the files specifically for the JCSP.NET Channel Name Service (CNS).

See:
Description

Interface Summary

CNSUser	Interface that a class can implement to indicate that instances allow channel names within a naming service to be managed.
LocationNotCNSRegisterable	This class should be implemented by NetChannelLocation objects which do not want to allow themselves to be registered with the Channel Name Server.
NamedChannelEndFactory	Classes implementing this interface act as factories for constructing NetChannelInput and NetChannelOutput objects.
NamedChannelEndManager	Classes implementing this interface act as factories for constructing NetChannelInput and NetChannelOutput objects (see NamedChannelEndFactory).

Class Summary

ChannelNameKey	Instances of this hold a key for a particular channel.
CNS	This class is the Channel Name Server's main server process class.
CNSChannelEndManager	This class implements the NamedChannelEndManager interface; providing methods for both constructing and destroying channels.
CNSNetChannelLocation	Instances of this class are returned by the resolve methods of CNSService.
CNSService	This class is the Channel Name Server's main client process class.
NameAccessLevel	This class allows name spaces to be identified around AbstractID objects (currently including ApplicationID, NodeID, DomainID and GlobalID ).

Exception Summary

ChannelNameException	An exception caused by an invalid channel name.
NameAccessLevelException	An exception caused by an invalid or misused NameAccessLevel.
WrongFactoryException	Thrown if an attempt is made to get a NamedChannelEndManager to destroy a channel that it did not create.

Package org.jcsp.net.cns Description

This package contains the files specifically for the JCSP.NET Channel Name Service (CNS). A CNS provides a broker service, enabling distributed JCSP processes to set up communications with each other. Networked channels have names. Currently, networked channels are automatically Any-One. The reading process is responsible for creating the channel and (optionally) registering it with a CNS with some unique (to the CNS) name. Writing processes need to know (or be told) the name of a networked channel to connect to it by the CNS. Communications between networked writers and reader then proceed directly (independent from the CNS).

See CNS and CNSService for information on the service.