public final class RemoteDisplay extends Object
Modifier and Type | Class and Description |
---|---|
static interface |
RemoteDisplay.Listener
Listener invoked when the remote display connection changes state.
|
Modifier and Type | Field and Description |
---|---|
static int |
DISPLAY_ERROR_CONNECTION_DROPPED |
static int |
DISPLAY_ERROR_UNKOWN |
static int |
DISPLAY_FLAG_SECURE |
Modifier and Type | Method and Description |
---|---|
void |
dispose()
Disconnects the remote display and stops listening for new connections.
|
protected void |
finalize()
Invoked when the garbage collector has detected that this instance is no longer reachable.
|
static RemoteDisplay |
listen(String iface,
RemoteDisplay.Listener listener,
Handler handler)
Starts listening for displays to be connected on the specified interface.
|
public static final int DISPLAY_FLAG_SECURE
public static final int DISPLAY_ERROR_UNKOWN
public static final int DISPLAY_ERROR_CONNECTION_DROPPED
protected void finalize() throws Throwable
Object
Note that objects that override finalize
are significantly more expensive than
objects that don't. Finalizers may be run a long time after the object is no longer
reachable, depending on memory pressure, so it's a bad idea to rely on them for cleanup.
Note also that finalizers are run on a single VM-wide finalizer thread,
so doing blocking work in a finalizer is a bad idea. A finalizer is usually only necessary
for a class that has a native peer and needs to call a native method to destroy that peer.
Even then, it's better to provide an explicit close
method (and implement
Closeable
), and insist that callers manually dispose of instances. This
works well for something like files, but less well for something like a BigInteger
where typical calling code would have to deal with lots of temporaries. Unfortunately,
code that creates lots of temporaries is the worst kind of code from the point of view of
the single finalizer thread.
If you must use finalizers, consider at least providing your own
ReferenceQueue
and having your own thread process that queue.
Unlike constructors, finalizers are not automatically chained. You are responsible for
calling super.finalize()
yourself.
Uncaught exceptions thrown by finalizers are ignored and do not terminate the finalizer thread. See Effective Java Item 7, "Avoid finalizers" for more.
public static RemoteDisplay listen(String iface, RemoteDisplay.Listener listener, Handler handler)
iface
- The interface address and port in the form "x.x.x.x:y".listener
- The listener to invoke when displays are connected or disconnected.handler
- The handler on which to invoke the listener.public void dispose()