java.lang.Object
mindbright.ssh.SSHClientUserAdaptor
mindbright.ssh.SSHSocketFactory
- All Implemented Interfaces:
- SSHClientUser
- public class SSHSocketFactory
- extends SSHClientUserAdaptor
NOLISTENPORT
public static final int NOLISTENPORT
- See Also:
- Constant Field Values
authenticator
protected SSHAuthenticator authenticator
clientCache
protected java.util.Hashtable clientCache
SSHSocketFactory
public SSHSocketFactory(java.lang.String host,
int port,
SSHAuthenticator authenticator)
SSHSocketFactory
public SSHSocketFactory(java.lang.String host,
SSHAuthenticator authenticator)
getClient
protected SSHClient getClient()
finalize
protected void finalize()
throws java.io.IOException
- 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.
addClient
protected void addClient(SSHClient client)
registerPseudoUser
protected void registerPseudoUser(SSHClient client,
SSHSocketImpl impl)
closePseudoAll
protected void closePseudoAll(SSHClient client)
closePseudoUser
protected void closePseudoUser(SSHClient client,
SSHSocketImpl u)
createSSHClient
protected SSHClient createSSHClient(int listenPort)
throws java.io.IOException
createSocketImpl
protected SSHSocketImpl createSocketImpl(SSHClient client,
boolean acceptor)
throws java.io.IOException
createSocket
public SSHSocket createSocket(java.lang.String address,
int port)
throws java.io.IOException
createServerSocket
public SSHServerSocket createServerSocket(int port,
int backlog)
throws java.io.IOException
createServerSocket
public SSHServerSocket createServerSocket(int port)
throws java.io.IOException
setServer
public void setServer(java.lang.String host,
int port)
setServer
public void setServer(java.lang.String host)
setAuthenticator
public void setAuthenticator(SSHAuthenticator authenticator)
open
public void open(SSHClient client)
connected
public void connected(SSHClient client)
disconnected
public void disconnected(SSHClient client,
boolean graceful)
report
public void report(java.lang.String msg)
alert
public void alert(java.lang.String msg)
JAVADOC | 
SOURCE | 
DOWNLOAD | NESTED | FIELD | CONSTR | METHOD