java.lang.Object
org.bluej.core.Hci
- public class Hci
- extends java.lang.Object
address
protected java.lang.String address
peer
protected int peer
closed
protected boolean closed
mon
protected Hci.Monitor mon
connections
protected java.util.Set connections
listener
protected L2CAPLstn listener
monThread
protected java.lang.Thread monThread
Hci
public Hci(int devid,
L2CAPLstn lstn)
throws BlueJException
Hci
public Hci()
throws BlueJException
Hci
public Hci(int devid)
throws BlueJException
Hci
public Hci(L2CAPLstn lstn)
throws BlueJException
getAddress
public java.lang.String getAddress()
close
public void close()
initialize
java.lang.String initialize(int devid)
throws BlueJException
connectL2CAP
public L2CAPConn connectL2CAP(long psm,
java.lang.String address,
int mtuIn,
int mtuOut)
throws BlueJException
listenStartL2CAP
public void listenStartL2CAP(long psm,
int mtuIn,
int mtuOut)
throws BlueJException
listenStopL2CAP
public void listenStopL2CAP(long psm)
throws BlueJException
acceptL2CAP
protected L2CAPConn acceptL2CAP()
throws BlueJException
discoverDevices
public java.lang.String[] discoverDevices(int inqSecs,
int maxDev)
throws BlueJException
closeDev
void closeDev()
connectionChange
void connectionChange(L2CAPConn conn,
boolean up)
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.