java.lang.Object
java.util.Observable
org.incenter.ngbclient.SocketAction
- All Implemented Interfaces:
- java.lang.Runnable
- public class SocketAction
- extends java.util.Observable
- implements java.lang.Runnable
thread
public java.lang.Thread thread
inStream
private java.io.BufferedReader inStream
outStream
protected java.io.BufferedWriter outStream
socket
private java.net.Socket socket
buffer
public java.lang.String buffer
SA_OPEN
public final int SA_OPEN
- See Also:
- Constant Field Values
SA_CLOSED
public final int SA_CLOSED
- See Also:
- Constant Field Values
SA_UNOPENED
public final int SA_UNOPENED
- See Also:
- Constant Field Values
SA_ERROR
public final int SA_ERROR
- See Also:
- Constant Field Values
status
public int status
telnet_mode
public boolean telnet_mode
TELCMD_IAC
public final int TELCMD_IAC
- See Also:
- Constant Field Values
TELCMD_DONT
public final int TELCMD_DONT
- See Also:
- Constant Field Values
TELCMD_DO
public final int TELCMD_DO
- See Also:
- Constant Field Values
TELCMD_WONT
public final int TELCMD_WONT
- See Also:
- Constant Field Values
TELCMD_WILL
public final int TELCMD_WILL
- See Also:
- Constant Field Values
TELCMD_SB
public final int TELCMD_SB
- See Also:
- Constant Field Values
TELCMD_NOP
public final int TELCMD_NOP
- See Also:
- Constant Field Values
TELCMD_SE
public final int TELCMD_SE
- See Also:
- Constant Field Values
TELOPT_BINARY
public final int TELOPT_BINARY
- See Also:
- Constant Field Values
TELOPT_ECHO
public final int TELOPT_ECHO
- See Also:
- Constant Field Values
TELOPT_TTYPE
public final int TELOPT_TTYPE
- See Also:
- Constant Field Values
TELQUAL_IS
public final int TELQUAL_IS
- See Also:
- Constant Field Values
TELQUAL_SEND
public final int TELQUAL_SEND
- See Also:
- Constant Field Values
SocketAction
public SocketAction()
run
public void run()
- Description copied from interface:
java.lang.Runnable
- This method will be called by whoever wishes to run your class
implementing Runnable. Note that there are no restrictions on what
you are allowed to do in the run method, except that you cannot
throw a checked exception.
- Specified by:
run in interface java.lang.Runnable
connect
public void connect(java.lang.String host,
int port)
throws java.lang.Exception
getInputStream
public java.io.InputStream getInputStream()
throws java.lang.Exception
isReady
private boolean isReady()
throws java.lang.Exception
readInt
private int readInt()
throws java.lang.Exception
sendInt
public void sendInt(int i)
throws java.lang.Exception
send
public void send(java.lang.String s)
throws java.lang.Exception
receive
public void receive()
throws java.lang.Exception
closeConnections
public void closeConnections()
throws java.lang.Exception
isConnected
public boolean isConnected()
finalize
protected void finalize()
- Description copied from class:
java.lang.Object
- Called on an object by the Virtual Machine at most once,
at some point after the Object is determined unreachable
but before it is destroyed. You would think that this
means it eventually is called on every Object, but this is
not necessarily the case. If execution terminates
abnormally, garbage collection does not always happen.
Thus you cannot rely on this method to always work.
For finer control over garbage collection, use references
from the
java.lang.ref package.
Virtual Machines are free to not call this method if
they can determine that it does nothing important; for
example, if your class extends Object and overrides
finalize to do simply super.finalize().
finalize() will be called by a java.lang.Thread that has no
locks on any Objects, and may be called concurrently.
There are no guarantees on the order in which multiple
objects are finalized. This means that finalize() is
usually unsuited for performing actions that must be
thread-safe, and that your implementation must be
use defensive programming if it is to always work.
If an Exception is thrown from finalize() during garbage
collection, it will be patently ignored and the Object will
still be destroyed.
It is allowed, although not typical, for user code to call
finalize() directly. User invocation does not affect whether
automatic invocation will occur. It is also permitted,
although not recommended, for a finalize() method to "revive"
an object by making it reachable from normal code again.
Unlike constructors, finalize() does not get called
for an object's superclass unless the implementation
specifically calls super.finalize().
The default implementation does nothing.