|
Class SlipChannel
|
The length indicator may optionally be followed by a configurable number of
blank padding bytes.
Clients of the SLIP protocol channel are not exposed to the header
information and receive/send only the payload information. The SlipChannel is
not aware of the payload contents. The contents are simply used as a sequence
of bytes.
SlipChannels are abstracted from their associated transport. That is the
underlying transport protocol may be assigned through configuration as long
as it adheres to the
com.newstep.solid.netio.StreamChannel constructs.
SlipChannels are based on the
com.newstep.solid.netio.MessageChannel construct and are
managed by and accessed through their associated SlipAccessPoint. The
SlipAccessPoint may be used both to listen for connections as server to
SlipChannels, and to create SlipChannels as a client and connect to a remote
end point.
As clients of their underlying transport channel the SlipChannel state
mimics that of its transport once it is assigned. Prior to assignment the
SlipChannel will remain in the CREATED state.
The length indicator may optionally be followed by a configurable number of
blank padding bytes.
Clients of the SLIP protocol channel are not exposed to the header
information and receive/send only the payload information. The SlipChannel is
not aware of the payload contents. The contents are simply used as a sequence
of bytes.
SlipChannels are abstracted from their associated transport. That is the
underlying transport protocol may be assigned through configuration as long
as it adheres to the
com.newstep.solid.netio.StreamChannel constructs.
SlipChannels are based on the
com.newstep.solid.netio.MessageChannel construct and are
managed by and accessed through their associated SlipAccessPoint. The
SlipAccessPoint may be used both to listen for connections as server to
SlipChannels, and to create SlipChannels as a client and connect to a remote
end point.
As clients of their underlying transport channel the SlipChannel state
mimics that of its transport once it is assigned. Prior to assignment the
SlipChannel will remain in the CREATED state.
The length indicator may optionally be followed by a configurable number of
blank padding bytes.
Clients of the SLIP protocol channel are not exposed to the header
information and receive/send only the payload information. The SlipChannel is
not aware of the payload contents. The contents are simply used as a sequence
of bytes.
SlipChannels are abstracted from their associated transport. That is the
underlying transport protocol may be assigned through configuration as long
as it adheres to the
com.newstep.solid.netio.StreamChannel constructs.
SlipChannels are based on the
com.newstep.solid.netio.MessageChannel construct and are
managed by and accessed through their associated SlipAccessPoint. The
SlipAccessPoint may be used both to listen for connections as server to
SlipChannels, and to create SlipChannels as a client and connect to a remote
end point.
As clients of their underlying transport channel the SlipChannel state
mimics that of its transport once it is assigned. Prior to assignment the
SlipChannel will remain in the CREATED state.
The length indicator may optionally be followed by a configurable number of
blank padding bytes.
Clients of the SLIP protocol channel are not exposed to the header
information and receive/send only the payload information. The SlipChannel is
not aware of the payload contents. The contents are simply used as a sequence
of bytes.
SlipChannels are abstracted from their associated transport. That is the
underlying transport protocol may be assigned through configuration as long
as it adheres to the
com.newstep.solid.netio.StreamChannel constructs.
SlipChannels are based on the
com.newstep.solid.netio.MessageChannel construct and are
managed by and accessed through their associated SlipAccessPoint. The
SlipAccessPoint may be used both to listen for connections as server to
SlipChannels, and to create SlipChannels as a client and connect to a remote
end point.
As clients of their underlying transport channel the SlipChannel state
mimics that of its transport once it is assigned. Prior to assignment the
SlipChannel will remain in the CREATED state.
| Field Summary | |
|---|---|
private final static String |
|
private static Logger |
|
protected SlipAccessPoint |
|
| Constructor Summary | |
|---|---|
void |
SlipChannel(SlipAccessPoint slipAccessPoint) |
| Method Summary | |
|---|---|
public synchronized void |
close() |
public ChannelEndpoint |
|
public ChannelEndpoint |
|
public void |
messageReceived(ProtocolMessage message) |
void |
setTransportChannel(StreamChannel transportChannel) |
public void |
stateChanged(CommChannelState newState) |
public String |
toString() |
public void |
write(Byte payload) |