Transport Channel Service
The Transport Channel Service is a highly flexible and scalable solution for client and server transports. Taking a protocol stack abstraction to building a transport, channels may be thought of as protocol layers in an OSI stack. Each channel provides very specific function as it relates to inter communication over networks or within processes.
The interfaces in this package are some of the interfaces accessible through the Transport Channel Service mbean. These interfaces will give the user specific information about the protocol stack, which is also known as Transport Chains or just simply Chains, and each of the layers within the stack, which are also known as Transport Channels or just simple Channels.
There are many pieces within this package which better describe the state of the configuration of the Channels and Chains. Here are just some of those elements:
- ChainData - This is the data about the specific Chain. This includes the list of channels in that chain.
- ChannelData - This is the data about the specific Channel. This includes the property lists for that channel, the factory name, and other important information.
- ChannelFactoryData - The ChannelFactory is the piece which creates the Channels. Because it knows about all the channels of a particular type (i.e. TCPChannel, HTTPChannel, WebContainerChannel, etc) the ChannelFactory may sometimes have specific resources allocated to it. So, some Channels will have configuration also for their factory.
- ChainGroupData - Within the Transport Channel Service, Chains may be grouped into logical groupings, called ChainGroups. This can further help facilitate the lifecycle methods for a group of chains. This group data will have a list of the Chains in that group.
- ChainStartMode - This interface helps facilitate the way a Chain is started within the framework.
- FlowType - This interface specifies the different types of Chains, Inbound or Outbound.
- Inbound - Inbound chains are the equivalent to server side chains. They will accept work into the system.
- Outbound - Outbound chains are the equivalent to client side chains. They will send work to another system.