public abstract class AltingConnectionServer<T> extends Guard implements ConnectionServer<T>
ALT
over a connection. Note that you cannot have
more than one server serving an AltingConnectionServer.ConnectionServer
,
ConnectionClient
,
Connection
FACTORY
Modifier | Constructor and Description |
---|---|
protected |
AltingConnectionServer(AltingChannelInput<org.jcsp.lang.ConnectionMessage<T>> altingChannel)
Constructor.
|
Modifier and Type | Method and Description |
---|---|
protected AltingChannelInput<org.jcsp.lang.ConnectionMessage<T>> |
getAltingChannel()
Returns the channel used to implement the Guard.
|
boolean |
pending()
Returns whether there is an open() pending on this connection.
|
protected void |
setAltingChannel(AltingChannelInput<org.jcsp.lang.ConnectionMessage<T>> chan)
ConnectionServer implementations are likely to be
implemented over channels. |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
reply, reply, replyAndClose, request
protected AltingConnectionServer(AltingChannelInput<org.jcsp.lang.ConnectionMessage<T>> altingChannel)
altingChannel
- The channel used to implement the Guardprotected AltingChannelInput<org.jcsp.lang.ConnectionMessage<T>> getAltingChannel()
protected void setAltingChannel(AltingChannelInput<org.jcsp.lang.ConnectionMessage<T>> chan)
ConnectionServer
implementations are likely to be
implemented over channels. Multiple channels from the client
to server may be used; one could be used for the initial
connection while another one could be used for data requests.
This method allows sub-classes to specify which channel should
be the next one to be alted over.chan
- the channel to be ALTed over.public boolean pending()
Note: if there is, it won't go away until you accept it. But if there isn't, there may be one by the time you check the result of this method.
Copyright © 1996–2020. All rights reserved.